> ## Documentation Index > Fetch the complete documentation index at: https://docs.tawked.com/llms.txt > Use this file to discover all available pages before exploring further. # Remove the logo > Drops the brand logo. A removal is not a brand change: the status stays as it is. The answer is the full row with `logo_url` null. Guide: [Applications](https://docs.tawked.com/partners/applications.md) ## OpenAPI ````yaml https://tawked.com/openapi.json delete /v1/partner/applications/{external_id}/logo openapi: 3.1.0 info: title: Tawked API version: 2026-09 summary: >- Tawked Verify: OTP verification for Saudi mobile numbers over SMS, in two calls. Tawked Notifications: WhatsApp template messages from the application's own number. Tawked Email: transactional e-mail from the application's own verified domain. Tawked Chat: the conversation menus a connected app adds beside the conversations of its connection's application, and the auto-attendant it sets up there. The Partner API for platforms that run Tawked Verify for their merchants. description: >- The public API of Tawked, a Saudi messaging platform: Tawked Verify (one-time codes), Tawked Notifications (WhatsApp templates from the application's own number), Tawked Email (transactional e-mail from the application's own domain) and the Partner API. Tawked Verify is an OTP verification API for Saudi numbers. One call sends a one-time code by SMS to a Saudi mobile number, and a second call checks it. SAR 0.09 per SMS code sent, prepaid; a send the network refuses is refunded. Authenticate with a Bearer API key from the dashboard (tk_live_ for production, tk_test_ for the sandbox, tk_partner_ for partners, tk_partner_test_ for the partner sandbox). Partners (tk_partner_) provision a Verify application per merchant under /v1/partner/applications and name it as application on every Verify call. Both /v1/... and /api/v1/... answer identically. Rate limit: 120 requests per minute per key. termsOfService: https://tawked.com/en/terms license: name: Proprietary (Tawked terms of service) url: https://tawked.com/en/terms contact: name: Tawked support email: support@tawked.com url: https://tawked.com/en/contact servers: - url: https://tawked.com description: Production (the sandbox is a tk_test_ key on the same host) - url: https://tawked.com/api description: The same API under /api/v1/..., kept for older integrations security: - bearerKey: [] - headerKey: [] tags: - name: Verify x-group: Verify description: Send and check one-time codes. - name: WhatsApp x-group: Notifications description: >- Tawked Notifications: send approved WhatsApp templates through the number connected to an application. An application in review or approved connects its own number from the dashboard. - name: Email x-group: Email description: >- Tawked Email: send transactional e-mail from an address on a verified domain of the application, to up to 50 recipients a message, in batches or scheduled, and read and list what was sent. Live keys only. - name: Chat x-group: Chat description: >- Tawked Chat: the conversation menus a connected app adds beside the conversations of its connection's application, and reads, changes and removes, with `chat:menus`; and the application's auto-attendant, which a connected app sets up, publishes and switches on or off, with `chat:attendant`. A connected app's key only; a business adds its own menus and builds its auto-attendant in the console. - name: Partner x-group: Partner API description: >- For platforms that run Tawked Verify for their merchants: provision a Verify application per merchant, keep its brand and verify settings current, switch it off and on, and read usage and the code log. Partner keys (tk_partner_) only; every Verify operation then takes `application` with the partner's own id for the application. - name: Webhooks x-group: Webhooks description: >- The events Tawked sends to your endpoint: an application's verification outcomes and message statuses, and a partner account's lifecycle, balance and opt-in verification events. Every delivery is signed the same way and retried the same way. externalDocs: description: Developer docs, with code samples url: https://docs.tawked.com paths: /v1/partner/applications/{external_id}/logo: delete: tags: - Partner summary: Remove the logo description: >- Drops the brand logo. A removal is not a brand change: the status stays as it is. The answer is the full row with `logo_url` null. operationId: partner_logo_remove parameters: - name: external_id in: path required: true schema: type: string description: Your own id for the application, as given at provisioning. - name: Idempotency-Key in: header required: false description: >- A 1 to 128 printable-ASCII key you generate, scoped to your API key. Replaying it with the same request answers the original 2xx unchanged, with the response header `Idempotent-Replayed: true`, and runs nothing again; the same key with another request answers `409 idempotency_key_reused`, and a request still in flight `409 idempotency_in_progress`. A refused request is never stored, so a corrected retry under the same key runs. Keys expire after 24 hours. schema: type: string responses: '200': description: Removed content: application/json: schema: type: object properties: service_id: type: string application_id: type: string external_id: type: string status: type: string screening: type: object properties: result: type: string rules: type: array items: type: - string - 'null' verify: type: object properties: code_length: type: integer ttl_seconds: type: integer max_attempts: type: integer max_per_hour: type: integer autofill_domain: type: string autofill_domain_enabled: type: boolean android_app_hash: type: - string - 'null' daily_spend_cap_halalas: type: - string - 'null' max_per_ip_per_hour: type: integer max_new_destinations_per_hour: type: integer paused: type: boolean name_ar: type: string name_en: type: string website: type: string industry: type: string merchant: type: object properties: registration_number: type: string contact_email: type: string logo_url: type: - string - 'null' metadata: type: object properties: plan: type: string status_message: type: - string - 'null' approved_at: type: string format: date-time disabled: type: boolean disabled_at: type: - string - 'null' archived: type: boolean archived_at: type: - string - 'null' paused_at: type: - string - 'null' pause_reason: type: - string - 'null' created_at: type: string format: date-time examples: removed: summary: Removed value: service_id: c2a10f3e-8b7a-4d2e-9c1a-1a2b3c4d5e6f application_id: c2a10f3e-8b7a-4d2e-9c1a-1a2b3c4d5e6f external_id: store_88 status: active screening: result: clean rules: [] verify: code_length: 6 ttl_seconds: 300 max_attempts: 3 max_per_hour: 5 autofill_domain: flowers.example autofill_domain_enabled: true android_app_hash: null daily_spend_cap_halalas: null max_per_ip_per_hour: 20 max_new_destinations_per_hour: 300 paused: false name_ar: متجر الورد name_en: Flower Shop website: https://flowers.example industry: ecommerce merchant: registration_number: '1010123456' contact_email: owner@flowers.example logo_url: null metadata: plan: pro status_message: null approved_at: '2026-09-02T09:00:00.000Z' disabled: false disabled_at: null archived: false archived_at: null paused_at: null pause_reason: null created_at: '2026-09-01T12:00:00.000Z' '401': description: >- `unauthorized`: Missing, unknown or revoked key; a key of another mode (`tk_live_` and `tk_test_` keys cannot call the partner API); or a partner account Tawked suspended.; `key_expired`: The key's `expires_at` has passed. Checked right after the key is recognised. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - unauthorized - key_expired '403': description: >- `ip_not_allowed`: The caller's IP is outside the key's allowlist.; `partner_suspended`: Your partner account was suspended by Tawked between the key check and the write. In practice the key already answers `401 unauthorized`; this is defense in depth.; `live_key_required`: A `tk_partner_test_` key on a management write. The sandbox key reads every partner endpoint and sends; use your live key to change anything. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - ip_not_allowed - partner_suspended - live_key_required '404': description: >- Unknown id / `not_found`: No application of yours has this `external_id`. Whether it exists under another partner is never revealed. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - not_found examples: unknown_id: summary: Unknown id value: error: not_found '409': description: >- `application_archived`: The application is archived. Restore it first; reads still work.; `idempotency_in_progress`: A request with this `Idempotency-Key` is still running. Wait for its answer, or retry in a moment.; `idempotency_key_reused`: This `Idempotency-Key` was already used for a different request (another body, path or method). Use one key per business event. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - application_archived - idempotency_in_progress - idempotency_key_reused '429': description: >- `too_many_requests`: Per-key rate limit exceeded (120 requests per minute, fixed 60-second window). Checked before authentication. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - too_many_requests '500': description: >- `internal_error`: An unhandled server error. Quote the X-Request-Id header if you report it. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - internal_error x-codeSamples: - lang: bash label: cURL source: >- curl -X DELETE https://tawked.com/v1/partner/applications/store_88/logo \ -H "Authorization: Bearer tk_partner_xxxxxxxxxxxxxxxxxxxx" - lang: javascript label: Node.js source: >- const res = await fetch("https://tawked.com/v1/partner/applications/store_88/logo", { method: "DELETE", headers: { Authorization: "Bearer tk_partner_xxxxxxxxxxxxxxxxxxxx", }, }); const data = await res.json(); - lang: python label: Python source: |- import requests res = requests.delete( "https://tawked.com/v1/partner/applications/store_88/logo", headers={"Authorization": "Bearer tk_partner_xxxxxxxxxxxxxxxxxxxx"}, ) data = res.json() components: schemas: Error: type: object required: - error properties: error: type: string description: A stable machine-readable code; the docs list every one. additionalProperties: true securitySchemes: bearerKey: type: http scheme: bearer description: >- Authorization: Bearer . An application key (tk_live_, tk_test_) has full access, which covers every product and any product added later, or custom access, chosen when the key is created: one or more of the scopes `verify:check`, `verify:send` (includes `verify:check`), `notifications:read`, `notifications:send` (includes `notifications:read`), `email:read`, `email:send` (includes `email:read`), `email:manage` (includes `email:send`), `webhooks:manage`, `email:inbound`, `notifications:templates` (includes `notifications:read`), `chat:menus`, `chat:attendant`. No key made on the API keys page holds `notifications:templates`, full access included: the three template writes answer such a key 403 `insufficient_scope`. A connected app's key holds it. Nor `chat:menus`: the five conversation menu operations answer such a key 403 `insufficient_scope`, and a connected app's key holds it once the client approved it. Nor `chat:attendant`: the five auto-attendant operations answer such a key 403 `insufficient_scope` too, and a connected app's key holds it once the client approved it. `email:manage` and `webhooks:manage` are held only by a key someone chose them for: a full-access key, old or new, never holds them. `email:inbound`, which reads, deletes and forwards received e-mail, is opt-in on every key, full access included: a key holds it only when it was turned on when the key was created. A call outside the key's access answers 403 `insufficient_scope` and names the scope it needs in the `WWW-Authenticate` response header. A partner key (tk_partner_) always has full access. Whatever its access, a key is a server-side secret. headerKey: type: apiKey in: header name: x-api-key description: >- The same API key, with the same access, as a header, for clients that cannot set Authorization. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.