> ## Documentation Index > Fetch the complete documentation index at: https://docs.agile-tools.io/llms.txt > Use this file to discover all available pages before exploring further. # Create person rate > Creates a person rate. Resolve the person id via GET /v1/public/people. Resolve the currency unit id via GET /v1/public/units. ## OpenAPI ````yaml /openapi.v1.local.json post /v1/public/person-rates openapi: 3.0.3 info: title: Agile Tools Public API description: >- REST API for integrating external systems with Agile Tools. ## Authentication Most endpoints require an `X-API-Key` header containing a valid owner-typed API key. Supported ownership types are `ORGANIZATION`, `PERSON`, and `VALUE_UNIT`. Anonymous library browsing endpoints use short-lived session tokens instead. ## Scope Behavior Wildcard scope (`*`) is organization-only. Value-unit keys are restricted to value-unit-centric endpoint families and descendant scope checks. Personal keys default to personal-empty scope unless explicit permissions are granted. Cross-organization key governance is out of scope for `/v1/public/*` and is handled by `/v1/sys/public-api-keys`. ## Rate Limiting Requests are rate-limited per API key based on your subscription plan. When a limit is exceeded the API returns `429 Too Many Requests` with a `Retry-After` header. ## Idempotency POST and PUT requests support idempotent replay via the optional `Idempotency-Key` header. Selected high-risk KPI and Health Metric write endpoints require this header to ensure safe retries without duplicate side-effects. ## Response Envelope Public v1 and v2 response contracts coexist during migration. Authenticated public endpoints use `PublicApiKeyMeta` semantics (`requestId`, `timestamp`) and anonymous public endpoints use `PublicAnonymousMeta` semantics. Anonymous library endpoints may add `PublicAnonymousLibraryMeta` tab-count metadata while authenticated public endpoints do not define a library tab-count metadata branch. ## Public Docs Visibility Policy Published public docs intentionally exclude anonymous Sessions and Library endpoints. Those v1 anonymous flows remain runtime-stable but are not listed in Mintlify-facing OpenAPI output. ## Migration Guidance For list endpoints, migrate in stages: keep v1 stable, adopt v2 offset mode first, then adopt v2 cursor mode where needed. Fallback expectation: clients may continue using v1 while v2 adoption is rolled out incrementally. ## Versioning & Deprecation Policy Breaking changes require a new major version (`/v2/`). Non-breaking additions ship in the current version. Deprecated endpoints include a `Sunset` HTTP header with the removal date. Minimum notice period: 6 months. contact: name: Agile Tools Developer Support url: https://teampoolz.mintlify.app email: dev-support@agile-tools.io version: 1.0.0 servers: - url: https://api.agile-tools.io description: Production - url: https://api.alpha.agile-tools.io description: Staging - url: https://free-trusty-kit.ngrok-free.app description: Local Development security: [] tags: - name: Address - name: Audit - name: Auth - name: Available scope - name: Billing Role - name: Billing Role Rate - name: Billing Role Rates - name: Billing Roles - name: Board - name: Budget - name: Budgets - name: Check In - name: Client - name: Client Project - name: Contact Info - name: Country - name: Demo Management - name: Goal - name: Goal Template - name: Goals - name: Group Notification Preferences - name: Groups description: Operations related to user groups - name: Health Metrics - name: Holiday Schemes - name: Hrosc - name: ISCO Groups - name: Integrations - name: Janitor System - name: Job Positions - name: KPIs - name: Key Result - name: Key Result Template - name: Key Results - name: Library Admin - name: Library Export - name: Library Import - name: Manager - name: Metric Period - name: Metric Template - name: Milestone - name: Nav Info - name: Newsletter - name: Notification Preferences - name: Observed Metrics - name: Org Account - name: Organizational Unit - name: Organizational Units - name: People - name: Person - name: Person Job Positions - name: Person Rate - name: Person Rates - name: Person Skills - name: Preferences - name: Public API Keys - name: Registration - name: SCM Repositories - name: Skills - name: Strategic Concept - name: Strategy - name: Stripe - name: Subscription - name: Sys Billing Role Rates - name: Sys Billing Roles - name: Sys Budgets - name: Sys Catalog - name: Sys Catalog Skill Groups - name: Sys Catalog Sync - name: Sys Check Ins - name: Sys Goals - name: Sys Job Positions - name: Sys Key Results - name: Sys Organizational Units - name: Sys Person - name: Sys Person Job Positions - name: Sys Person Rates - name: Sys Person Skills - name: Sys Public API Keys - name: Sys Skills - name: Sys Tags - name: Sys Teams - name: Sys Value Items - name: Sys Value Units - name: Tag - name: Tags - name: Team - name: Teams - name: Time zones - name: Timesheet - name: Timesheet Export - name: Timesheet Period Configuration - name: Timesheet Period Management - name: Timesheet Periods - name: Unit - name: Value Item - name: Value Item Settings - name: Value Items - name: Value Unit - name: Value Units - name: Webhooks - name: Workboards - name: Workflow - name: Workload Schemes - name: Worklog Approvals Configuration - name: Worklog Conflicts - name: Worklog Scheduler Configuration - name: Worklogs paths: /v1/public/person-rates: post: tags: - Person Rates summary: Create person rate description: >- Creates a person rate. Resolve the person id via GET /v1/public/people. Resolve the currency unit id via GET /v1/public/units. operationId: createPublicPersonRate requestBody: description: >- Create payload for a person rate. Resolve personId via GET /v1/public/people. Resolve currencyUnitId via GET /v1/public/units. content: application/json: schema: $ref: '#/components/schemas/PublicPersonRateCreateDto' examples: create person rate: value: personId: 0f3e8793-4caf-4705-826d-491e25988924 costRate: 45 billingRate: 90 currencyUnitId: 7c9e6679-7425-40de-944b-e07fc1f90ae7 effectiveDate: '2026-01-01' externalId: PERSON_RATE_2026_Q1 required: true responses: '200': description: Person rate created content: application/json: schema: $ref: '#/components/schemas/PublicPersonRateDto' examples: created person rate: value: data: id: 2f6db7d4-6e6c-4d4f-90f2-cbaac8441f7b personId: 0f3e8793-4caf-4705-826d-491e25988924 personName: Calvin Tyler Osborne costRate: 45 billingRate: 90 currencyUnitId: 7c9e6679-7425-40de-944b-e07fc1f90ae7 effectiveDate: '2026-01-01' externalId: PERSON_RATE_2026_Q1 meta: requestId: f056699e-497d-41d9-a877-d7c862de6587 timestamp: '2026-04-03T12:08:00Z' '400': description: Invalid create payload '404': description: Person or currency unit not found '409': description: externalId already in use in this organization security: - apiKey: [] components: schemas: PublicPersonRateCreateDto: required: - personId - costRate - billingRate - currencyUnitId - effectiveDate type: object properties: personId: description: >- Id of the person the rate applies to. Resolve via GET /v1/public/people. maxLength: 100 pattern: \S type: string example: 0f3e8793-4caf-4705-826d-491e25988924 costRate: description: Fully-loaded internal cost per hour (burn-down source). minimum: 0 pattern: ^\d{1,10}([.]\d{1,2})?$ type: number example: 45 billingRate: description: External client price per hour (not consumed by budgets). minimum: 0 pattern: ^\d{1,10}([.]\d{1,2})?$ type: number example: 90 currencyUnitId: description: Id of the currency unit. Resolve via GET /v1/public/units. maxLength: 100 pattern: \S type: string example: 7c9e6679-7425-40de-944b-e07fc1f90ae7 effectiveDate: description: Date the rate becomes effective (day-based semantics). type: string allOf: - $ref: '#/components/schemas/LocalDate' example: '2026-01-01' externalId: description: >- Optional external system identifier. Must be unique within the organization. maxLength: 255 type: string example: PERSON_RATE_2026_Q1 PublicPersonRateDto: type: object properties: id: type: string personId: type: string personName: type: string costRate: type: number billingRate: type: number currencyUnitId: type: string effectiveDate: $ref: '#/components/schemas/LocalDate' externalId: type: string LocalDate: format: date type: string example: '2022-03-10' securitySchemes: apiKey: type: apiKey description: >- Owner-typed API key (`ORGANIZATION`, `PERSON`, `VALUE_UNIT`). Manage org-scoped lifecycle with `/v1/public-api-keys`; cross-org governance is restricted to `/v1/sys/public-api-keys`. name: X-API-Key in: header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.