Send the Pixelbase team a request

Send a request to the Pixelbase team — for something Pixelbase can’t do for you yet, or that a tool can’t reach. It goes to Pixelbase, not to your own customers or company, and lands in the same inbox as the website’s Contact Us form, where the team is notified. Use it when what was asked has no tool, or the person can’t or won’t grant the permission it needs — and only after the person has read the message and said yes to sending it. `name`, `email` and `phone` default to the signed-in person’s own, so usually only `message` is needed. `context` says what you were attempting: put what they asked for in `request`, the tool or capability that was missing or blocked in `blocked`, and the scopes you were refused in `missingScopes`. Pixelbase records the connection, the person and their company itself; don’t repeat them. At most 5 requests an hour per connection and 10 a day per person.

Required scope

The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Dev Tools → API, to an assistant or CLI sign-in when you approve or edit it under Dev Tools, and to a teammate under Employee → Permissions.

inquiries:write

Request Body

Property	Type	Required	Description
`message`	string	Required	What the person wants, in their words and enough for the team to act on without asking again. Up to 2,000 characters.
`name`	string	Optional	Who it is from. Defaults to the signed-in person’s name.
`email`	string	Optional	Where the team replies. Defaults to the signed-in person’s email.
`phone`	string	Optional	A number the team can reach them on. Defaults to the signed-in person’s.
`context`	object	Optional	What you were attempting: `request` (what the person asked for), `blocked` (the tool or capability that was missing or blocked), `missingScopes` (scopes you were refused), `notes`.

POSTExample request

curl

curl -X POST "https://www.pxb.app/api/public/v1/contact-inquiries" \
  -H "Authorization: Bearer your_access_token" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "I’d like to export last year’s invoices as a single PDF for my accountant. There doesn’t seem to be a way to do that from here.",
    "context": {
      "request": "Export all 2025 invoices as one PDF",
      "blocked": "No tool for bulk invoice PDF export",
      "missingScopes": []
    }
  }'

200Example response

json

{
  "message": "Request sent to the Pixelbase team.",
  "content": {
    "inquiry": {
      "id": "inq_3e8c"
    }
  }
}

In the console

The same thing done by hand, for anyone comparing the API against the screen they already use.

Threads → Support

/threads