> ## Documentation Index > Fetch the complete documentation index at: https://docs.fourdos.dev/llms.txt > Use this file to discover all available pages before exploring further. # Grant a consent or accept an agreement > Records the member's acceptance of `version` of `scope`. The scope must be a live consent item that is your organization's or the platform's, and the version must be in effect now. Granting the version already active is a no-op that answers 200; granting a different version supersedes the active one. A grant after a withdrawal inserts a new row, so the history reads grant, withdraw, grant. Recorded with `source: "api"`. A member session can call this for its own user id. ## OpenAPI ````yaml https://api.develop.fourdos.dev/openapi/partner.json post /v1/users/{userId}/consents openapi: 3.1.0 info: title: 4D OS Partner API version: 0.1.0 description: >- REST API for 4D OS partners. Authenticate with your organization API key: `Authorization: Bearer `. Requests and responses are JSON with `snake_case` field names. Errors share one envelope: `{ "error": { "code", "status", "message", "details"? } }`. Mutating endpoints that declare it accept an `Idempotency-Key` header so retries are safe. Bulk-migrating members? See the [Migrating to 4D guide](https://docs.fourdos.dev/walkthroughs/migrate-existing-members) for the canonical import schema, a worked example, and the `/v1/imports` sequence. servers: - url: https://api.develop.fourdos.dev security: - partnerApiKey: [] tags: - name: Users description: Create, read, and manage users and their org membership - name: Imports description: Bulk member import jobs (staging → validate → commit) - name: Consents description: Record, list and withdraw a member's consents and agreements - name: Rewards description: A member's reward catalog, claims and reward codes - name: XP description: >- A member's balance, earning headroom, expiry and boosts, and what each event pays - name: Tiers description: Read your organization's tier ladder - name: Webhooks description: Register webhook endpoints. Deliveries are not sent yet. - name: Events description: Refetch your organization's events from the last 30 days - name: API keys description: Issue, list, and revoke server-side organization API keys - name: Modules description: >- Publish private modules, install visible modules, and manage their credentials - name: Ingest description: Receive signed native events from an installed module - name: Engagement description: Browser event tracking (publishable keys) and tracking-key management - name: Revenue description: Report sales and refunds for the club's revenue dashboards - name: Ad delivery description: Fill a club site's ad slots, for anonymous or signed-in fans - name: Ad entries description: Fans entering a sponsor's draw, reported by the club's backend paths: /v1/users/{userId}/consents: post: tags: - Consents summary: Grant a consent or accept an agreement description: >- Records the member's acceptance of `version` of `scope`. The scope must be a live consent item that is your organization's or the platform's, and the version must be in effect now. Granting the version already active is a no-op that answers 200; granting a different version supersedes the active one. A grant after a withdrawal inserts a new row, so the history reads grant, withdraw, grant. Recorded with `source: "api"`. A member session can call this for its own user id. operationId: grantConsent parameters: - name: userId in: path required: true schema: type: string - name: Idempotency-Key in: header required: false description: >- Same key and request replays the original response; same key with a different body is `409 IDEMPOTENCY_CONFLICT`. schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/GrantConsentBody' responses: '200': description: The same version was already active; nothing changed content: application/json: schema: $ref: '#/components/schemas/Consent' '201': description: Consent recorded content: application/json: schema: $ref: '#/components/schemas/Consent' '401': description: '`UNAUTHORIZED`: no valid credential' content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: '`NOT_FOUND`: the user is not a member of your organization' content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: >- `IDEMPOTENCY_CONFLICT`: the `Idempotency-Key` was already used with a different body content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: >- `VALIDATION_ERROR`: the body failed validation; no live item exists for `scope` (`details.scope`, `details.lifecycle`, which is null for an unknown scope or another organization's); or `version` is not in effect (`details.scope`, `details.version`) content: application/json: schema: $ref: '#/components/schemas/Error' security: - partnerApiKey: [] - adminSession: [] - memberSession: [] components: schemas: GrantConsentBody: type: object properties: scope: type: string minLength: 1 version: type: integer exclusiveMinimum: 0 maximum: 9007199254740991 required: - scope - version Consent: type: object properties: id: type: string scope: type: string version: type: integer minimum: -9007199254740991 maximum: 9007199254740991 granted_at: type: string revoked_at: type: - string - 'null' source: type: string enum: - api - ui - migration required: - id - scope - version - granted_at - revoked_at - source additionalProperties: false Error: type: object properties: error: type: object properties: code: type: string status: type: integer message: type: string details: type: object additionalProperties: true required: - code - status - message required: - error securitySchemes: partnerApiKey: type: http scheme: bearer description: >- Organization API key (`org_...`) sent as `Authorization: Bearer `. Keys are scoped to one organization; every request operates within that tenant. adminSession: type: http scheme: bearer description: >- Partner admin session token sent as `Authorization: Bearer `. Obtained by signing in (console or the email OTP endpoints) and completing the second factor; see the Authentication page. memberSession: type: http scheme: bearer description: >- A signed-in member's session token sent as `Authorization: Bearer `. Accepted only on the operations that list it, and each of those says which user ids a member may name. Your backend uses the organization API key instead. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.