API Reference

Tickets

Support ticket workflows, category management, and message actions.

Lists accessible support tickets or returns a single ticket when ticketId is provided.

Authentication

Session.

Modes: logged-in user, API key

API key: tickets:read

Permissions or Scopes

owner, category viewer/responder, or manage_tickets

Request Headers

Header	Value	Description
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
page	query	No	Page number for paginated results.
pageSize	query	No	Requested page size where supported by the endpoint.
ticketId	query	No	Ticket ID for detail lookup.
categoryId	query	No	Filter by category.
status	query	No	open, closed, claimed, or all.
mine	query	No	Restrict to current user tickets.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets', {
  method: 'GET',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.get('https://playroom.date/api/tickets', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "tickets": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Page (query)Page number for paginated results.Page Size (query)Requested page size where supported by the endpoint.Ticket Id (query)Ticket ID for detail lookup.Category Id (query)Filter by category.Status (query)open, closed, claimed, or all.Mine (query)Restrict to current user tickets.

Request

GET /api/tickets?page=1&pageSize=20

curl Equivalent

curl "https://playroom.date/api/tickets?page=1&pageSize=20"

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "tickets": []
  },
  "error": null
}

Creates a support ticket for the current user.

Authentication

Session + CSRF.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

current user

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
title	body	Yes	Ticket title, 3-120 characters.
categoryId	body	Yes	Ticket category ID.
message	body	Yes	Initial ticket message, 5-2000 characters.

Validation

Title is 3-120 characters.
Message is 5-2000 characters.
Category ID is required.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X POST -H "Authorization: Bearer prapi_your_key" -H "Content-Type: application/json" -d '{"title":"Example title","categoryId":"category_id","message":"example-message"}' "https://playroom.date/api/tickets"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets', {
  method: 'POST',
  headers: {
    "Authorization": "Bearer prapi_your_key",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "title": "Example title",
    "categoryId": "category_id",
    "message": "example-message"
  }),
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.post('https://playroom.date/api/tickets', headers=headers, json={"title": "Example title", "categoryId": "category_id", "message": "example-message"})
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "ticket": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Title * (body)Ticket title, 3-120 characters.Category Id * (body)Ticket category ID.Message * (body)Initial ticket message, 5-2000 characters.

Request

POST /api/tickets

Request Payload

{
  "title": "Example ticket",
  "categoryId": "",
  "message": "Example message"
}

curl Equivalent

curl -X POST -H "Content-Type: application/json" -d '{"title":"Example ticket","categoryId":"","message":"Example message"}' "https://playroom.date/api/tickets"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "ticket": []
  },
  "error": null
}

Updates ticket status, claim state, or metadata according to caller permissions.

Authentication

Session + CSRF.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

owner, responder, or manage_tickets

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
ticketId	body	Yes	Ticket ID to update.
status	body	No	Updated ticket status.
claimedByMe	body	No	Claim or unclaim the ticket as the current user.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X PUT -H "Authorization: Bearer prapi_your_key" -H "Content-Type: application/json" -d '{"ticketId":"ticket_id","status":"","claimedByMe":true}' "https://playroom.date/api/tickets"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets', {
  method: 'PUT',
  headers: {
    "Authorization": "Bearer prapi_your_key",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "ticketId": "ticket_id",
    "status": "",
    "claimedByMe": true
  }),
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.put('https://playroom.date/api/tickets', headers=headers, json={"ticketId": "ticket_id", "status": "", "claimedByMe": True})
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "ticket": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Ticket Id * (body)Ticket ID to update.Status (body)Updated ticket status.Claimed By Me (body)Claim or unclaim the ticket as the current user.

Request

PUT /api/tickets

Request Payload

{
  "ticketId": ""
}

curl Equivalent

curl -X PUT -H "Content-Type: application/json" -d '{"ticketId":""}' "https://playroom.date/api/tickets"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "ticket": []
  },
  "error": null
}

Deletes a ticket when caller has management permission.

Authentication

Session + CSRF.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

manage_tickets

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
ticketId	query	Yes	Ticket ID to delete.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X DELETE -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets?ticketId=ticket_id"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets?ticketId=ticket_id', {
  method: 'DELETE',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.delete('https://playroom.date/api/tickets?ticketId=ticket_id', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "ticket": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Ticket Id * (query)Ticket ID to delete.

Request

DELETE /api/tickets

curl Equivalent

curl -X DELETE "https://playroom.date/api/tickets"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "ticket": []
  },
  "error": null
}

Deletes a ticket message according to ticket and moderation permissions.

Authentication

Session + CSRF.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

message owner, responder, or manage_tickets

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
messageId	query	Yes	Message ID to delete.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X DELETE -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets/messages?messageId=message_id"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/messages?messageId=message_id', {
  method: 'DELETE',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.delete('https://playroom.date/api/tickets/messages?messageId=message_id', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "message": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Message Id * (query)Message ID to delete.

Request

DELETE /api/tickets/messages

curl Equivalent

curl -X DELETE "https://playroom.date/api/tickets/messages"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "message": []
  },
  "error": null
}

Lists support ticket categories and viewer role configuration.

Authentication

Session or actor-linked API key.

Modes: logged-in user, API key

API key: tickets:read

Permissions or Scopes

current user or manage_tickets

Request Headers

Header	Value	Description
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
No path, query, or body parameters.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets/categories"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/categories', {
  method: 'GET',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.get('https://playroom.date/api/tickets/categories', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "categories": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

This request has no editable path, query, or body fields.

Request

GET /api/tickets/categories

curl Equivalent

curl "https://playroom.date/api/tickets/categories"

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "categories": []
  },
  "error": null
}

Creates a ticket category.

Authentication

Admin session + CSRF or actor-linked API key.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

define_tickets

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
name	body	Yes	Category name.
description	body	No	Optional category description.
color	body	No	Optional hex color.
responderRoleIds	body	No	Responder role IDs.
viewerRoleIds	body	No	Viewer role IDs.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X POST -H "Authorization: Bearer prapi_your_key" -H "Content-Type: application/json" -d '{"name":"example-name","description":"example-description","color":"example-color","responderRoleIds":[],"viewerRoleIds":[]}' "https://playroom.date/api/tickets/categories"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/categories', {
  method: 'POST',
  headers: {
    "Authorization": "Bearer prapi_your_key",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "name": "example-name",
    "description": "example-description",
    "color": "example-color",
    "responderRoleIds": [],
    "viewerRoleIds": []
  }),
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.post('https://playroom.date/api/tickets/categories', headers=headers, json={"name": "example-name", "description": "example-description", "color": "example-color", "responderRoleIds": [], "viewerRoleIds": []})
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "category": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Name * (body)Category name.Description (body)Optional category description.Color (body)Optional hex color.Responder Role Ids (body)Responder role IDs.Viewer Role Ids (body)Viewer role IDs.

Request

POST /api/tickets/categories

Request Payload

{
  "name": "",
  "responderRoleIds": [],
  "viewerRoleIds": []
}

curl Equivalent

curl -X POST -H "Content-Type: application/json" -d '{"name":"","responderRoleIds":[],"viewerRoleIds":[]}' "https://playroom.date/api/tickets/categories"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "category": []
  },
  "error": null
}

Updates a ticket category and viewer role settings.

Authentication

Admin session + CSRF or actor-linked API key.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

define_tickets

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
categoryId	body	Yes	Category ID to update.
name	body	Yes	Category name.
description	body	No	Optional category description.
color	body	No	Optional hex color.
responderRoleIds	body	No	Responder role IDs.
viewerRoleIds	body	No	Viewer role IDs.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X PUT -H "Authorization: Bearer prapi_your_key" -H "Content-Type: application/json" -d '{"categoryId":"category_id","name":"example-name","description":"example-description","color":"example-color","responderRoleIds":[],"viewerRoleIds":[]}' "https://playroom.date/api/tickets/categories"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/categories', {
  method: 'PUT',
  headers: {
    "Authorization": "Bearer prapi_your_key",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "categoryId": "category_id",
    "name": "example-name",
    "description": "example-description",
    "color": "example-color",
    "responderRoleIds": [],
    "viewerRoleIds": []
  }),
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.put('https://playroom.date/api/tickets/categories', headers=headers, json={"categoryId": "category_id", "name": "example-name", "description": "example-description", "color": "example-color", "responderRoleIds": [], "viewerRoleIds": []})
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "category": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Category Id * (body)Category ID to update.Name * (body)Category name.Description (body)Optional category description.Color (body)Optional hex color.Responder Role Ids (body)Responder role IDs.Viewer Role Ids (body)Viewer role IDs.

Request

PUT /api/tickets/categories

Request Payload

{
  "categoryId": "",
  "name": "",
  "responderRoleIds": [],
  "viewerRoleIds": []
}

curl Equivalent

curl -X PUT -H "Content-Type: application/json" -d '{"categoryId":"","name":"","responderRoleIds":[],"viewerRoleIds":[]}' "https://playroom.date/api/tickets/categories"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "category": []
  },
  "error": null
}

Deletes a ticket category and associated viewer permissions.

Authentication

Admin session + CSRF or actor-linked API key.

Modes: logged-in user, API key

API key: tickets:write

Permissions or Scopes

define_tickets

Request Headers

Header	Value	Description
Cookie	session=<session_cookie>	Session cookie set by the login flow.
x-csrf-token	<csrfToken>	Required for mutating session-authenticated requests.
Content-Type	application/json	Required when sending a JSON body.
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
categoryId	query	Yes	Category ID to delete.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -X DELETE -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets/categories?categoryId=category_id"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/categories?categoryId=category_id', {
  method: 'DELETE',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.delete('https://playroom.date/api/tickets/categories?categoryId=category_id', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "category": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

Category Id * (query)Category ID to delete.

Request

DELETE /api/tickets/categories

curl Equivalent

curl -X DELETE "https://playroom.date/api/tickets/categories"

I understand this request can change or delete application data.

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "category": []
  },
  "error": null
}

Returns whether the current user can access ticket functionality.

Authentication

Session.

Modes: logged-in user, API key

API key: tickets:read

Permissions or Scopes

current user

Request Headers

Header	Value	Description
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
No path, query, or body parameters.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets/access"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/access', {
  method: 'GET',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.get('https://playroom.date/api/tickets/access', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "access": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

This request has no editable path, query, or body fields.

Request

GET /api/tickets/access

curl Equivalent

curl "https://playroom.date/api/tickets/access"

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "access": []
  },
  "error": null
}

Returns a count of open tickets visible to the caller.

Authentication

Session.

Modes: logged-in user, API key

API key: tickets:read

Permissions or Scopes

current user or manage_tickets

Request Headers

Header	Value	Description
Authorization	Bearer prapi_your_key	Preferred API-key header. Never send API keys in URLs.
x-api-key	prapi_your_key	Alternative API-key header.
x-api-token	prapi_your_key	Legacy API-key header kept for backward compatibility.

Parameters

Name	In	Required	Description
No path, query, or body parameters.

Validation

Request parameters and JSON payloads are validated server-side.
Mutating session-authenticated requests require CSRF validation.
Permission checks run before privileged data is returned or modified.

Errors

400 Invalid input, missing parameters, or validation failure.

401 Authentication is missing or invalid.

403 The authenticated principal lacks the required permission or scope.

404 The requested resource was not found.

500 Unexpected server error.

Rate Limits

No endpoint-specific public rate limit is documented. Authentication and abuse controls still apply.

Examples and Try It

Request examples, sample output, and the live tester below apply only to this endpoint.

cURL

curl -H "Authorization: Bearer prapi_your_key" "https://playroom.date/api/tickets/open-count"

JavaScript / TypeScript

const response = await fetch('https://playroom.date/api/tickets/open-count', {
  method: 'GET',
  headers: {
    "Authorization": "Bearer prapi_your_key"
  },
});
const data = await response.json();

Python

import requests

headers = {"Authorization": "Bearer prapi_your_key"}
response = requests.get('https://playroom.date/api/tickets/open-count', headers=headers)
print(response.json())

Example Output

{
  "success": true,
  "data": {
    "count": []
  },
  "error": null
}

Try It

Checking sign-in state...

Auth: No authentication

This request has no editable path, query, or body fields.

Request

GET /api/tickets/open-count

curl Equivalent

curl "https://playroom.date/api/tickets/open-count"

Sample Response

Sample Response Body

{
  "success": true,
  "data": {
    "count": []
  },
  "error": null
}