> ## Documentation Index > Fetch the complete documentation index at: https://developers.1-funnel.org/llms.txt > Use this file to discover all available pages before exploring further. # Invalidate an OTP challenge > Terminal invalidation. Consistent with single-use verification — an invalidated challenge cannot be verified afterward. ## OpenAPI ````yaml /specs/external-integration-api.openapi.yaml post /v1/businesses/{businessId}/otp/challenges/{challengeId}/invalidate openapi: 3.1.0 info: title: 1Funnel External Integration API version: 0.1.0-draft summary: External Integration API — Developer Preview (contract only, non-GA). description: | OpenAPI 3.1 for the **1Funnel External Integration API** (foundation through webhooks). Companion AsyncAPI documents outbound webhook event payloads. ## Status (read carefully) | Layer | Status | |-------|--------| | Architecture (Platform ADRs / STD-API-01) | Approved | | This OpenAPI document | **Developer Preview — contract only** (non-GA) | | Sandbox API host | Architecture **target** — not claimed operational | | Production API host | Architecture **target** — not claimed operational | This specification is published for integrator review. Documented endpoints and authentication services are **not** available for public integration. Sandbox and production availability will be announced separately. This is not general availability (ADR-011 DEC-5A-07 Preview API documentation). ## Authentication and authorization Callers authenticate with OAuth 2.0 Client Credentials (`client_secret_basic`) against the external authorization server (ADR-015, ADR-023). Access tokens must present audience `1funnel-external-api`. After token validation, every business-scoped operation requires: 1. Valid application identity 2. Active application-to-business grant for `{businessId}` 3. Required resource permission (ADR-022) 4. Resource ownership / isolation (ADR-016) `{businessId}` is a selector, not proof. OAuth scopes (when introduced) are coarse token vocabulary and are **not** the ADR-022 permission catalogue. Operations document required permissions with `x-required-permissions`. ## Servers and OAuth URLs API `servers` and OAuth token URLs are environment-specific architecture targets (ADR-023). OpenAPI cannot automatically switch the OAuth `tokenUrl` when a client selects a `servers` entry. See `x-1funnel-oauth` and the security scheme description. contact: name: 1Funnel Platform email: support@1funnel.ng license: name: Proprietary url: https://1funnel.ng servers: - url: https://api.1-funnel.org description: | Production External Integration API host (ADR-023 target). Not claimed deployed or generally available. - url: https://api.sandbox.1-funnel.org description: | Sandbox External Integration API host (ADR-023 target). Not claimed deployed or generally available. security: - OAuth2ClientCredentials: [] tags: - name: Foundation description: Shared conventions and cross-cutting components. - name: SMS description: | Individual SMS, bulk SMS, reporting, and SMS templates (ADR-018). Public bulk resource is `/sms/bulk-messages`. There is no `/sms/batches`. - name: Wallet description: Read-only wallet balance (ADR-019). - name: OTP description: | Managed OTP challenges (ADR-020 / ADR-008). Secrets are never returned. Service availability is not claimed by this draft. - name: Webhooks description: | Webhook endpoint management, event history, and delivery inspection (ADR-021). Signature protocol DEC-WH-S01 approved. Ownership verification deferred in v1. Public manual replay and public secret rotation are not available. See WEBHOOK-DECISION-REGISTER.md. paths: /v1/businesses/{businessId}/otp/challenges/{challengeId}/invalidate: parameters: - $ref: '#/components/parameters/BusinessId' - $ref: '#/components/parameters/ChallengeId' post: tags: - OTP summary: Invalidate an OTP challenge description: | Terminal invalidation. Consistent with single-use verification — an invalidated challenge cannot be verified afterward. operationId: invalidateOtpChallenge parameters: - $ref: '#/components/parameters/RequestId' requestBody: required: false content: application/json: schema: $ref: '#/components/schemas/OtpInvalidateRequest' examples: cancel: value: reason: user_cancelled responses: '200': description: Challenge invalidated headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/json: schema: $ref: '#/components/schemas/OtpChallenge' examples: invalidated: value: id: 018f3c4e-7b2a-7c3d-8e9f-dddddddddddd business_id: 018f3c4e-7b2a-7c3d-8e9f-0123456789ab status: invalidated purpose: login channel: sms delivery_mode: inline code_length: 6 expires_at: '2026-10-13T09:05:00.000Z' resend_available_at: null remaining_resends: 0 attempt_count: 0 max_verification_attempts: 5 verified_at: null invalidated_at: '2026-10-13T09:02:00.000Z' created_at: '2026-10-13T09:00:00.000Z' updated_at: '2026-10-13T09:02:00.000Z' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '409': description: Challenge already in a terminal state headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: alreadyConsumed: value: type: >- https://developers.1-funnel.org/problems/otp_challenge_consumed title: Challenge already consumed status: 409 detail: The challenge was already verified. code: otp_challenge_consumed request_id: req_01HZX3K9EXAMPLE '422': $ref: '#/components/responses/UnprocessableContent' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/InternalServerError' '503': $ref: '#/components/responses/ServiceUnavailable' components: parameters: BusinessId: name: businessId in: path required: true description: > Business resource selector in `/v1/businesses/{businessId}/…` (ADR-006). UUIDv7-compatible opaque identifier. `{businessId}` is **not** authorization proof. The resource server must independently verify an active application-to-business grant, required permission, and ownership (ADR-016, ADR-022). schema: $ref: '#/components/schemas/UuidV7' examples: grantedBusiness: summary: Example business id value: 018f3c4e-7b2a-7c3d-8e9f-0123456789ab ChallengeId: name: challengeId in: path required: true description: OTP challenge identifier (UUIDv7). schema: $ref: '#/components/schemas/UuidV7' RequestId: name: X-Request-Id in: header required: false description: > Request correlation identifier (STD-API-01 D12). Clients may supply a value of 1–128 characters matching `A-Za-z0-9._-`. Missing or invalid values are replaced by a server-generated identifier. Distinct from W3C `traceparent`, resource ids, `Idempotency-Key`, and webhook event ids. schema: type: string minLength: 1 maxLength: 128 pattern: ^[A-Za-z0-9._-]+$ examples: - req_01HZX3K9EXAMPLE schemas: OtpInvalidateRequest: type: object description: Invalidate (cancel) an open challenge. Terminal after success. additionalProperties: false properties: reason: type: string minLength: 1 maxLength: 64 description: Optional machine-readable reason (e.g. user_cancelled). examples: - user_cancelled examples: - reason: user_cancelled OtpChallenge: type: object description: > Public OTP challenge representation. Never includes plaintext codes, hashes, Redis keys, or rendered message bodies (ADR-020 / ADR-008). additionalProperties: false required: - id - business_id - status - purpose - channel - code_length - expires_at - created_at - updated_at properties: id: $ref: '#/components/schemas/UuidV7' business_id: $ref: '#/components/schemas/UuidV7' status: $ref: '#/components/schemas/OtpChallengeStatus' purpose: $ref: '#/components/schemas/OtpPurpose' channel: $ref: '#/components/schemas/OtpChannel' delivery_mode: $ref: '#/components/schemas/OtpDeliveryMode' code_length: type: integer minimum: 4 maximum: 12 expires_at: $ref: '#/components/schemas/Timestamp' resend_available_at: oneOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' remaining_resends: type: - integer - 'null' minimum: 0 attempt_count: type: - integer - 'null' minimum: 0 max_verification_attempts: type: - integer - 'null' minimum: 1 verified_at: oneOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' invalidated_at: oneOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' created_at: $ref: '#/components/schemas/Timestamp' updated_at: $ref: '#/components/schemas/Timestamp' examples: - id: 018f3c4e-7b2a-7c3d-8e9f-dddddddddddd business_id: 018f3c4e-7b2a-7c3d-8e9f-0123456789ab status: queued purpose: login channel: sms delivery_mode: inline code_length: 6 expires_at: '2026-10-13T09:05:00.000Z' resend_available_at: '2026-10-13T09:01:00.000Z' remaining_resends: 4 attempt_count: 0 max_verification_attempts: 5 verified_at: null invalidated_at: null created_at: '2026-10-13T09:00:00.000Z' updated_at: '2026-10-13T09:00:00.000Z' ProblemDetails: type: object description: > RFC 9457 Problem Details for HTTP APIs (`application/problem+json`). STD-API-01 D08 requires `type`, `title`, `status`, `detail`, `code`, and `request_id`. `instance` is recommended. Validation failures include `errors`. Problem `type` namespace (DEC-SMS-E01): `https://developers.1-funnel.org/problems/{code}` These identifiers do not imply documentation pages are deployed. Resolvable problem-type documentation is required before GA. additionalProperties: true required: - type - title - status - detail - code - request_id properties: type: type: string format: uri-reference description: >- Problem class identifier using the developers.1-funnel.org namespace. examples: - https://developers.1-funnel.org/problems/validation_failed title: type: string description: Short, stable summary safe for clients. examples: - Validation failed status: type: integer minimum: 100 maximum: 599 description: HTTP status code for this occurrence. examples: - 400 detail: type: string description: >- Occurrence-specific explanation. Must not include secrets or stack traces. examples: - The request failed validation. instance: type: string format: uri-reference description: URI reference for this occurrence (RFC 9457 SHOULD). code: $ref: '#/components/schemas/ProblemCode' request_id: type: string minLength: 1 maxLength: 128 pattern: ^[A-Za-z0-9._-]+$ description: Same value as response header `X-Request-Id` (STD-API-01 MUST). examples: - req_01HZX3K9EXAMPLE errors: type: array description: >- Present for validation failures (STD-API-01). Each item has `pointer` and `code`. items: type: object additionalProperties: false required: - pointer - code properties: pointer: type: string description: JSON Pointer into the request body, or a query parameter name. code: type: string description: Stable field-level error code. examples: - type: https://developers.1-funnel.org/problems/validation_failed title: Validation failed status: 400 detail: The request failed validation. instance: /v1/businesses/018f3c4e-7b2a-7c3d-8e9f-0123456789ab/sms/messages code: validation_failed request_id: req_01HZX3K9EXAMPLE errors: - pointer: /to code: field_invalid UuidV7: type: string format: uuid pattern: >- ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$ description: > UUID with version nibble `7` (UUIDv7). STD-API-01 prefers UUIDv7 for new platform-generated external resource identifiers. Clients must still treat the value as opaque. Not every path parameter is guaranteed to be v7 solely because it is a UUID; use this schema where the contract asserts UUIDv7. examples: - 018f3c4e-7b2a-7c3d-8e9f-0123456789ab OtpChallengeStatus: type: string description: > Publicly safe challenge lifecycle status (lowercase snake_case). Distinct from SMS delivery lifecycle (ADR-020 OTP-A05). Never implies code exposure. enum: - queued - sent - verified - expired - locked - invalidated - failed_delivery examples: - queued - verified OtpPurpose: type: string description: > Challenge purpose (lowercase snake_case public enum; ADR-020 OTP-A01). Exact allowed set is policy-controlled; values below are the initial catalogue. enum: - login - register - password - transfer - merchant_custom examples: - login OtpChannel: type: string description: >- Delivery channel. SMS is the initial approved channel (ADR-020 / ADR-008). enum: - sms examples: - sms OtpDeliveryMode: type: string description: How the OTP message content was selected at create time. enum: - template - inline examples: - inline Timestamp: type: string format: date-time description: > RFC 3339 date-time. Response timestamps are UTC with a `Z` offset (STD-API-01 D06). Client-supplied timestamps must include an explicit offset; local times without an offset are rejected. examples: - '2026-10-13T09:00:00.000Z' ProblemCode: type: string description: | Stable machine-readable Problem Details `code` values for the External Integration API. Type URI form: `https://developers.1-funnel.org/problems/{code}`. Resolvable problem-type documentation is required before GA; these identifiers do not imply pages are deployed today. enum: - validation_failed - authentication_required - permission_denied - resource_not_found - idempotency_conflict - recipient_limit_exceeded - sender_not_authorized - template_not_active - invalid_recipient - rate_limit_exceeded - service_unavailable - internal_error - balance_unavailable - otp_verification_failed - otp_challenge_expired - otp_challenge_locked - otp_challenge_consumed - otp_challenge_invalidated - otp_resend_cooldown - otp_resend_limit_exceeded examples: - validation_failed - otp_verification_failed headers: RequestIdResponse: description: > Correlation identifier for this response (STD-API-01 D12). Echoes a valid client `X-Request-Id` or a server-generated value. schema: type: string minLength: 1 maxLength: 128 pattern: ^[A-Za-z0-9._-]+$ examples: - req_01HZX3K9EXAMPLE RetryAfter: description: > Hint for when the client may retry (for example 429 or 503). Value may be delay-seconds or an HTTP-date per RFC 9110. schema: type: string examples: - '60' responses: Unauthorized: description: | Unauthorized — missing or invalid authentication (`code: authentication_required`, DEC-SMS-E01). headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: authenticationRequired: value: type: >- https://developers.1-funnel.org/problems/authentication_required title: Authentication required status: 401 detail: A valid OAuth 2.0 access token is required. code: authentication_required request_id: req_01HZX3K9EXAMPLE Forbidden: description: > Forbidden — authenticated caller lacks required permission, business grant, or sender authorization (`permission_denied` or `sender_not_authorized`). Cross-business existence may be concealed with 404 instead (ADR-016). headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: permissionDenied: value: type: https://developers.1-funnel.org/problems/permission_denied title: Forbidden status: 403 detail: >- The application is not permitted to perform this operation for the selected business. code: permission_denied request_id: req_01HZX3K9EXAMPLE senderNotAuthorized: value: type: https://developers.1-funnel.org/problems/sender_not_authorized title: Sender not authorized status: 403 detail: The sender identity is not authorized for this business. code: sender_not_authorized request_id: req_01HZX3K9EXAMPLE NotFound: description: | Not Found — resource missing or concealed under authorization policy (`code: resource_not_found`, DEC-SMS-E01 / ADR-016). headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: notFound: value: type: https://developers.1-funnel.org/problems/resource_not_found title: Not found status: 404 detail: The requested resource was not found. code: resource_not_found request_id: req_01HZX3K9EXAMPLE UnprocessableContent: description: > Unprocessable Content — syntactically valid request that cannot be processed due to semantic constraints (DEC-SMS-E01). Examples include recipient limit, inactive template, or invalid recipient. headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: recipientLimit: summary: Bulk recipient limit exceeded value: type: >- https://developers.1-funnel.org/problems/recipient_limit_exceeded title: Recipient limit exceeded status: 422 detail: >- The request exceeds the maximum of 1000 submitted recipient entries. code: recipient_limit_exceeded request_id: req_01HZX3K9EXAMPLE templateNotActive: value: type: https://developers.1-funnel.org/problems/template_not_active title: Template not active status: 422 detail: The template is archived or not active for new submissions. code: template_not_active request_id: req_01HZX3K9EXAMPLE invalidRecipient: value: type: https://developers.1-funnel.org/problems/invalid_recipient title: Invalid recipient status: 422 detail: One or more recipients failed semantic validation. code: invalid_recipient request_id: req_01HZX3K9EXAMPLE TooManyRequests: description: | Too Many Requests — rate limit exceeded (`code: rate_limit_exceeded`, DEC-SMS-E01). headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' Retry-After: $ref: '#/components/headers/RetryAfter' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: rateLimited: value: type: https://developers.1-funnel.org/problems/rate_limit_exceeded title: Rate limit exceeded status: 429 detail: The client has exceeded an applicable rate limit. code: rate_limit_exceeded request_id: req_01HZX3K9EXAMPLE InternalServerError: description: Internal Server Error — unexpected failure. headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: internal: value: type: https://developers.1-funnel.org/problems/internal_error title: Internal server error status: 500 detail: An unexpected error occurred. code: internal_error request_id: req_01HZX3K9EXAMPLE ServiceUnavailable: description: | Service Unavailable (`code: service_unavailable`, DEC-SMS-E01). headers: X-Request-Id: $ref: '#/components/headers/RequestIdResponse' Retry-After: $ref: '#/components/headers/RetryAfter' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' examples: unavailable: value: type: https://developers.1-funnel.org/problems/service_unavailable title: Service unavailable status: 503 detail: The service is temporarily unavailable. code: service_unavailable request_id: req_01HZX3K9EXAMPLE securitySchemes: OAuth2ClientCredentials: type: oauth2 description: > OAuth 2.0 Client Credentials for the External Integration API (ADR-015, ADR-023). Client authentication: HTTP Basic (`client_secret_basic`). Access-token audience: `1funnel-external-api`. The `tokenUrl` below is the **production** target. Sandbox uses a different host. OpenAPI cannot bind `tokenUrl` to the selected `servers` entry; see `x-1funnel-oauth` on the root document and the authentication guide when published. Coarse OAuth scopes (if any) are token-level vocabulary (ADR-013 IA-06). They are **not** the ADR-022 resource permission catalogue. Resource permissions are enforced after token validation via application-to-business grants (ADR-016) and are documented per operation with `x-required-permissions`. These URLs are architecture targets. They are not claimed to be deployed or generally available. flows: clientCredentials: tokenUrl: https://auth.1-funnel.org/oauth2/token scopes: {} x-1funnel-client-authentication: client_secret_basic x-1funnel-audience: 1funnel-external-api ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.