> ## Documentation Index > Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt > Use this file to discover all available pages before exploring further. # Set the number-ownership webhook URL > Set the HTTPS URL that receives number-ownership events for this enterprise: `number_reputation.number.flagged`, `number_reputation.number.removed` and `number_reputation.external_verification.status_changed`. Send `webhook_url: null` to stop receiving them. ## OpenAPI ````yaml /openapi/source/external/number-reputation/number-reputation.json patch /enterprises/{enterprise_id}/reputation/webhook openapi: 3.1.0 info: x-latency-category: responsive title: Telnyx Number Reputation API version: 2.0.0 description: >- The Telnyx Number Reputation API lets you monitor the spam-score / reputation of your phone numbers on US/CA carrier networks. Register a phone number for reputation monitoring, submit a Letter of Authorization (LOA) so carriers honor your remediation requests, refresh scores on a schedule, and inspect reputation history over time. Flow: create an enterprise, register it for Number Reputation, submit the LOA, add phone numbers, then read their reputation data and trends. Number Reputation is billable - see https://telnyx.com/pricing/numbers for current pricing. contact: email: support@telnyx.com servers: - url: https://api.telnyx.com/v2 description: Telnyx API v2 (production) security: - bearerAuth: [] tags: - name: Terms of Service description: >- Accept and review the Branded Calling and Phone Number Reputation terms of service. - name: Reputation description: Phone-number reputation monitoring (spam-score lookup and tracking). - name: Enterprises description: Manage the legal-entity record that owns your DIRs and phone numbers. paths: /enterprises/{enterprise_id}/reputation/webhook: patch: tags: - Reputation summary: Set the number-ownership webhook URL description: >- Set the HTTPS URL that receives number-ownership events for this enterprise: `number_reputation.number.flagged`, `number_reputation.number.removed` and `number_reputation.external_verification.status_changed`. Send `webhook_url: null` to stop receiving them. operationId: updateReputationWebhook parameters: - $ref: '#/components/parameters/EnterpriseId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/EnterpriseReputationWebhookUpdate' example: webhook_url: https://example.com/webhooks/telnyx responses: '200': description: Updated reputation settings. content: application/json: schema: $ref: '#/components/schemas/EnterpriseReputationPublicWrapped' '400': $ref: '#/components/responses/GenericErrorResponse' '401': $ref: '#/components/responses/GenericErrorResponse' '404': $ref: '#/components/responses/GenericErrorResponse' components: parameters: EnterpriseId: name: enterprise_id in: path description: The enterprise id. Lowercase UUID. required: true schema: type: string format: uuid example: 4a6192a4-573d-446d-b3ce-aff9117272a6 schemas: EnterpriseReputationWebhookUpdate: type: object required: - webhook_url properties: webhook_url: type: - string - 'null' format: uri maxLength: 2048 description: >- HTTPS URL on a publicly routable host. Send `null` to stop receiving number-ownership events. example: https://example.com/webhooks/telnyx EnterpriseReputationPublicWrapped: type: object required: - data properties: data: $ref: '#/components/schemas/EnterpriseReputationPublic' EnterpriseReputationPublic: type: object properties: enterprise_id: type: string format: uuid example: 4a6192a4-573d-446d-b3ce-aff9117272a6 status: $ref: '#/components/schemas/ReputationStatus' check_frequency: $ref: '#/components/schemas/ReputationCheckFrequency' loa_document_id: type: - string - 'null' description: Id of the signed LOA document. example: 2a7e8337-e803-4057-a4ae-26c40eb0bc6c loa_status: $ref: '#/components/schemas/ReputationLoaStatusPublic' rejection_reasons: type: - array - 'null' items: type: string description: Populated when `status` is `rejected`. external_verification_status: anyOf: - $ref: '#/components/schemas/ExternalVerificationStatus' - type: 'null' description: >- Review state of the enterprise's ownership proof for numbers hosted with another provider. `null` when no proof was submitted. webhook_url: type: - string - 'null' format: uri description: >- HTTPS URL that receives number-ownership webhook events for this enterprise. example: https://example.com/webhooks/telnyx created_at: type: string format: date-time example: '2026-04-26T18:06:51.940749Z' readOnly: true updated_at: type: string format: date-time example: '2026-04-26T18:09:24.785211Z' readOnly: true Errors: type: object required: - errors properties: errors: type: array items: $ref: '#/components/schemas/Error' description: List of one or more error entries. Order is not significant. description: >- Canonical Telnyx error envelope. Returned on every 4xx and 5xx response from this service. `errors` is non-empty; multiple entries indicate multiple distinct problems with the same request (e.g. one entry per invalid phone number on a bulk operation). ReputationStatus: type: string enum: - pending - approved - deleted - rejected description: Lifecycle status of the enterprise's Phone Number Reputation activation. ReputationCheckFrequency: type: string enum: - business_daily - daily - weekly - biweekly - monthly - never description: >- How often Telnyx refreshes the stored reputation data for this enterprise's registered numbers. ReputationLoaStatusPublic: type: string enum: - pending - approved - rejected description: >- Customer-facing Letter-of-Authorization verification state. `approved` is required (alongside reputation status) before phone numbers can be added. example: pending ExternalVerificationStatus: type: string enum: - pending - approved - rejected description: >- Review state of the ownership proof that allows adding phone numbers hosted with another provider. example: pending Error: type: object required: - code - title - detail - meta properties: code: type: string example: '10005' description: >- Stable numeric Telnyx error catalog id. See `meta.url` for the full catalog entry. title: type: string example: Invalid parameters description: >- Short human-readable category, e.g. `Bad Request`, `Duplicate resource`, `Not Found`, `Forbidden`. Treat as advisory only - the stable identifier is `code`. detail: type: string example: field required description: >- Context-specific message describing what went wrong on this particular request. May embed offending values; do not rely on it for programmatic matching - branch on `code`. meta: type: object required: - url properties: url: type: string format: uri example: https://developers.telnyx.com/docs/overview/errors/10005 pending_check_ids: type: array items: type: string format: uuid description: >- Set on `422 vetting_checks_incomplete` responses from `/admin/dir/{id}/approve` and `/admin/phone-number-batches/approve`. Lists the still-pending vetting check ids. pending_check_codes: type: array items: type: string description: >- Codes of the pending vetting checks (e.g. `loa_signature_valid`). pending_check_labels: type: array items: type: string description: Human-readable labels of the pending vetting checks. description: >- Carries `url` linking to the Telnyx error catalog entry for this `code`. Useful for forwarding the user to documentation. source: type: object description: Optional pointer at the offending field of the request. properties: pointer: type: string example: /body/legal_name parameter: type: string example: page[size] description: >- A single entry in the canonical Telnyx error envelope. `code` is the stable Telnyx error catalog id; the human-readable explanation lives at `meta.url`. `detail` is a context-specific message; `source.pointer` (when present) names the offending field of the request. responses: GenericErrorResponse: description: >- An error occurred. The response carries the standard Telnyx error envelope. content: application/json: schema: $ref: '#/components/schemas/Errors' examples: validation_error: summary: 422 - request body failed validation value: errors: - code: '10005' title: Invalid parameters detail: field required meta: url: https://developers.telnyx.com/docs/overview/errors/10005 source: pointer: /body/legal_name bad_request: summary: 400 - request rejected by a state guard description: >- Returned when the request itself is well-formed but the resource is in a state that disallows this action (e.g. updating a DIR while it is being vetted, or deleting an enterprise that still has DIRs in vetting). value: errors: - code: '10015' title: Bad Request detail: Cannot update DIR in 'verified' status meta: url: https://developers.telnyx.com/docs/overview/errors/10015 not_found: summary: 404 - resource does not exist or is not yours value: errors: - code: '10009' title: Resource not found detail: Enterprise not found. meta: url: https://developers.telnyx.com/docs/overview/errors/10009 conflict: summary: 409 - request conflicts with current resource state value: errors: - code: '10021' title: Resource in use detail: >- DIR has 1 active infringement claim(s). Resolve the claim before making this change. meta: url: https://developers.telnyx.com/docs/overview/errors/10021 securitySchemes: bearerAuth: type: http scheme: bearer description: >- Telnyx API key. Generate one at https://portal.telnyx.com/#/app/api-keys. ````