List your notifications
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/notifications/v1-current-user-feed-index.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
GET/
Lists your notifications on this team, newest first: activity that concerns you, such as new comments, customer replies, payments received and approvals answered.
By default only unseen, unarchived items are returned. Send not_seen_yet=0 to include seen items, and show_archive=1 to include archived ones too (it adds them; it does not return only archived items). The page size is your team's list size setting (50 unless changed).
Customer Portal payment notifications (type customer_payment) are listed only when your role may see that customer's finances; others are left out of the page and of the total.
Business rules
not_seen_yetandshow_archivetake1or0.trueandfalseare refused.- A
customer_paymentnotification is listed for the team owner, or for a role with View Customer Sales Aggregates and Manage Customers ("Manage All", or "Manage Assigned to User" when the customer is assigned to you). Itspayment.affected_orderslists only the orders you may see, and none without View Sales Order Pricing. - Access is checked again for each row: if you lose access after a payment notification was listed, it comes back with
actionpayment_access_changed,message_keycustomer_payment.payment_access_changedandobject[]. - A key whose user is no longer a member of the team gets an empty list.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
Query parameters
not_seen_yetinteger1(default): only unseen items.0: seen and unseen.- One of:
0,1 - Default
1 - Example
0
- One of:
show_archiveinteger0(default): leave out archived items.1: include them.- One of:
0,1 - Default
0 - Example
0
- One of:
pageinteger- Default
1 - Minimum 1
- Default
Request body
This operation takes no request body.
Response
200Successful response.
Fields of each item (5)
activityobjectWhat happened.
Child fields (7)
actionstringWhat happened. For
customer_payment:dispute_opened,dispute_under_review,dispute_won,funds_withheld,chargeback_confirmed,payment_reversed,payment_needs_attention,deadline_approaching,deadline_overdue,funds_released,funds_restored,case_won_awaiting_funds,payment_resolved,provider_refund_appliedorprovider_refund_failed;payment_access_changedwhen you can no longer see that payment.created_atstring (date-time)idstringmessage_keystringIdentifies the kind of notification, for your own wording:
<type>.<action>, such asorder.new_comment.objectobject | arrayThe details, which depend on the kind: for example the order, the comment and who wrote it (
user:id,name,avatar_url). An empty array[]when there are none. Forcustomer_payment, the payment as it was then (payment, with the orders it touched inpayment.affected_orders, limited to the ones you may see);[]when you can no longer see that payment.teamobjecttypestringWhat the notification is about, such as
order.customer_paymentfor Customer Portal payment events (disputes, chargebacks, refunds and holds).
archivebooleancreated_atstring (date-time)idstringThe feed item id. Use it with the mark operations.
seenboolean
paginationobjectChild fields (6)
Links to the neighbouring pages:
previousandnext, each present only when that page exists. An empty list,[], when there is only one page.
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.422The request was refused and changed nothing.
validation_failedlists what to fix inerror.fields; other codes name a business rule, explained inerror.message. A few checks answer with only{"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answerconnect_timeout("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.- When
not_seen_yetorshow_archiveis not0or1(validation_failed;error.fieldsnames the field).- Fix
- Send
1or0.
Related
- PUTMark notifications as seen
/v1/ api/ store/ {team_slug}/ current_user_feed/ seen - PUTMark all your notifications as seen
/v1/ api/ store/ {team_slug}/ current_user_feed/ mark_all_as_seen - PUTArchive notifications
/v1/ api/ store/ {team_slug}/ current_user_feed/ archive
