Skip to main content

API Key

You must first create an API Key in Wavelength. It is located under “Manage Integrations”, then scroll to the bottom and click “Manage API Keys”. Here, you can see your existing keys, their names and expiration. You can delete existing ones. When creating a new API key, the name must be unique in your organization. Once the key has been created, you will be shown a one-time dialog box with your new API key. You should copy this down somewhere safe — we will not show this again. If you lose your API key, you will need to make a new one. For these endpoints, set the Authorization header to your API key value directly (for example Authorization: <API_KEY>). Do not add a Bearer prefix; the full header value is validated as the key.

Sending Events

Here is the API endpoint for sending events to Wavelength. The only required field is query:
If you want to specify who is sending/creating the ticket, include a user. The user must have at least one of these fields: email, source_specific_id, or id (the Wavelength ID). We will match the user to an existing Wavelength customer/contact based on these fields. If no matching Wavelength user exists, the user will be created. Other optional fields include name, username, image_url. If you want to match the interaction to a specific company account, please include the company_source_specific_id or the company_id (the company’s Wavelength ID). You can also pass in other optional fields like the title, original timestamp, and additional attributes.

Source Specific ID

You can include a source_specific_id to give the ticket a unique identifier. This is useful for:
  • Deduplication: Prevent duplicate tickets from being created
  • Replying: Use this ID later to add replies to the ticket via the /interactions/reply endpoint
You can then reply to this ticket using the source_specific_id:

Full Example with All Fields

You can also pass in a base64 encoded image if you prefer, or an image URL:
You can attach multiple images by passing in multiple files.
The files field is used to send images to Wavelength. You can currently send JPG and PNG images up to 4MB in size. Here are some of the errors that may be returned:
  • 400: Invalid request - missing title, file too large, couldn’t be opened, etc.
  • 401: Invalid API Key or expired API Key
  • 503: Wavelength server error has been logged and our team has been notified
Errors take on the following format in JSON:
Successful responses take on the following format in JSON:

Rate Limiting

There is a rate limit of 30 events per second. If you exceed this, you will receive a 429 response code. If you need a higher rate, please let us know.

List Interactions

GET /interactions

Returns a paginated list of interactions (top-level tickets) for your organization.

Query Parameters

Example: List all interactions

Example: Filter by status

Example: Filter by multiple statuses

Example: Filter by source

Example: Filter by source (multiple)

Example: Filter by category

Example: Filter by tag

Example: Filter by team owner

Example: Incremental sync (interactions updated in the last 24 hours)

Response

Error Responses


Get Interaction with History

GET /interactions/:id

Returns a single interaction and its full reply/message thread.

Path Parameters

Example

Response

The history array contains all messages, replies, and internal notes for the interaction in chronological order. The from field identifies the message author. For Gmail interactions, to and cc are included when available.

Error Responses


List Teams

GET /teams

Returns all teams in your organization. Use team IDs with the team_owner_id filter on GET /interactions.

Example

Response

Error Responses


List Categories

GET /categories

Returns all categories in your organization. Use category IDs with the category_id filter on GET /interactions.

Example

Response

Error Responses


List Tags

GET /tags

Returns all account tags in your organization. Use tag IDs with the tag_id filter on GET /interactions.

Example

Response

Error Responses


Create Interaction Reply

POST /interactions/reply

Creates a new reply/message for an existing ticket. Supports multiple ticket identification methods and file attachments.

Query Parameters

Exactly one of the following is required:

Headers

  • Content-Type: multipart/form-data (required for file uploads)
  • Authorization: <API_KEY> (required; raw key, no Bearer prefix)

Request Body (multipart/form-data)

User Object

*At least one of id or email is required. If only email is provided, it will be used as the user identifier.

Ticket Identification

The endpoint requires exactly one query parameter for ticket identification:
  • id - Wavelength ULID of the ticket
  • source_specific_id - Source-specific ID of the ticket
Both parameters cannot be provided simultaneously, and at least one is required.

Example Request (with Wavelength ULID)

Example Request (with source_specific_id)

Example Request (with file uploads)

Response

Error Responses

400 Bad Request

404 Not Found

409 Conflict (Duplicate)

413 Payload Too Large

Important Notes

  • File Size Limit: 32MB per file
  • Supported File Types: Any file type can be uploaded
  • Deduplication: Duplicate source_specific_id values are rejected for Slack/Community Slack sources
  • User Requirement: User object with user.id is now mandatory (no anonymous users)
  • Query Parameter Exclusivity: Exactly one of id or source_specific_id must be provided, not both
  • Rate Limiting: Subject to rate limiting (60 requests per minute per API key/IP)