---
title: "Get a profile's queue"
method: GET
path: "/profiles/{id}/queue"
tags: ["Profiles"]
---

# Get a profile's queue

`GET /profiles/{id}/queue`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/profiles/{id}/queue`
- Auth: HTTP bearer

Its posting times, read in its time zone; the next `count` times free for at least one of its accounts, with which ones (none of them has a post at that minute, scheduled or queued, and none would pass its network's daily cap); and its queued posts still to go out.

## Path parameters

- `id` string, required: The profile's id (`prof_`).

## Query parameters

- `count` integer: How many free times to list.

## Response `200`

OK

- Queue
  - `profileId` string, required
  - `timeZone` string, required: The profile's time zone, which the slots are read in.
  - `slots` QueueSlot[], required: Its posting times, Monday first, each day's in order.
    - `weekday` 'mon' | 'tue' | 'wed' | 'thu' | 'fri' | 'sat' | 'sun', required
    - `time` string, required: A local time, HH:mm, in the profile's time zone: the same clock time all year, across summer time.
  - `next` object[], required: The next posting times free for at least one of the profile's accounts, to show what is open. Never copy one into `scheduledAt` to take it: two callers would take the same one. Create the post with `queue: true` instead.
    - `at` string, date-time, required
    - `accountIds` string[], required: The profile's accounts free then: none of them has a post at that minute, and none would pass its network's daily cap.
  - `posts` object[]: The queued posts still to go out, soonest first, the next 100 at most, with their accounts (`Get a post` has the rest). Left out for a key or agent without `posts:read`: the queue's own read scope is `accounts:read`.
    - `id` string, required
    - `scheduledAt` string, date-time, required
    - `accountIds` string[], required

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `404`: `not_found`: No such object, or it is outside your team or the profiles your key reaches.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
