Skip to content

API reference

Resend inbox support address test

support.ResendInboxSupportAddressTestWriteAPI key

Resend a verification email for a pending inbox support address.

POST/v1/operations/support.ResendInboxSupportAddressTest
On this page

Access & visibility

Allow support.ResendInboxSupportAddressTest on your API key.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

inbox_idstringRequired

Use the support inbox record's top-level id, not its slug or forwarding address. support.ListInboxes.

At least 1 character.

idstringRequired

Additional address id from ListInboxSupportAddresses.items for this same inbox_id. It is not the email address, inbox ID, or a verification token.

At least 1 character.

Verify forwarding before using a support address

Get the inbox_id and forwarding address from List inbox channels. Configure your mail provider to forward the public support address into that inbox, then add the address. Adding it sends a verification email; the address becomes verified only when that email is forwarded back into the correct Brigg inbox.

List support addresses to check verifiedAt. A test=sent response only confirms a send attempt; it is not verification. Only the newest test can verify, and it expires after 24 hours. Fix forwarding before requesting another test. Verification permits that address to be used as Reply-To for its conversations; it does not change the authenticated sender.

Removing the address withdraws its verified Reply-To use. It does not remove your mail provider's forwarding rule or delete the inbox and its conversations. Change provider forwarding separately when retiring the address.

Response

Returns 200 OK with a JSON body.

teststringRequired

sent confirms a test email was sent; already_verified sends nothing; send_failed means delivery could not be initiated. Verification still requires the email to return through the inbox. Send throttling is HTTP 429 rate_limited, not a successful test value.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Too many verification sends. Existing limits are ten per inbox and thirty per workspace per hour; wait before a new test action.
409 org_not_provisioned Finish inbox-forwarding setup in Brigg before requesting verification.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "inbox_id": {
      "type": "string",
      "minLength": 1,
      "description": "Use the support inbox record's top-level id, not its slug or forwarding address. [support.ListInboxes](/reference/support/ListInboxes)."
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Additional address id from ListInboxSupportAddresses.items for this same inbox_id. It is not the email address, inbox ID, or a verification token."
    }
  },
  "required": [
    "inbox_id",
    "id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "inbox_id": "e_inbox_support",
      "id": "isa_help"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "test": {
      "type": "string",
      "description": "sent confirms a test email was sent; already_verified sends nothing; send_failed means delivery could not be initiated. Verification still requires the email to return through the inbox. Send throttling is HTTP 429 rate_limited, not a successful test value."
    }
  },
  "required": [
    "test"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "test": "sent"
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.