Mobile

3 operations. Call each with POST https://app.chirply.io/api/v1/actions/<name> and a bearer token; the response is { "data": { "action", "summary", "result" } }. A read badge means the operation changes nothing; write requires the credential’s write scope.

Request mobile app access

mobile.request_test_accesswriteconfirm

Ask for an email address to be added to a Chirply mobile app's store tester list, and alert the Chirply team that it is waiting. This does NOT install anything or grant access: a person has to type the address into Google Play Console (or App Store Connect) by hand, usually within a day, and the requester is emailed once that happens. The address must be the one the device's store account uses — a Google account for Android, an Apple ID for iPhone — which is often not the address they sign in to Chirply with; the app will not appear for any other account. Submitting the same address again bumps the existing request rather than queueing it twice. Costs nothing.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Also answers to join the beta, add me to the android test, get on the tester list.

Parameters

Field	Type	Required	Description
platform	"android" \| "ios"	required	Which app: 'android' (Google Play) or 'ios' (the iPhone app, on the App Store).
email	string	required	The email address on the store account — the Google account the phone's Play Store is signed in to, or the Apple ID. Stored lowercased. Not validated beyond its shape: only the store console can confirm it exists.

Example

curl -X POST https://app.chirply.io/api/v1/actions/mobile.request_test_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "android",
    "email": "ada@example.com"
  }'

Test with your API key

Over MCP the same operation is the tool mobile_request_test_access at https://app.chirply.io/api/mcp, same bearer token, same input.

Mobile apps

mobile.statusread

Report where each Chirply mobile app is up to — Android on Google Play and the iPhone app on the App Store — and every request this account has made to be let into one. An app in 'closed_test' is not publicly installable: it only appears for store accounts a person has added to the tester list, so an install link is useless until a request comes back 'added'. Reads only; changes nothing and sends nothing.

Also answers to get the mobile app, android app, iphone app, download the app.

Parameters

Field	Type	Required	Description
platform	"android" \| "ios"	optional	Only report on this app. Omit for both.

Example

curl -X POST https://app.chirply.io/api/v1/actions/mobile.status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "android"
  }'

Test with your API key

Over MCP the same operation is the tool mobile_status at https://app.chirply.io/api/mcp, same bearer token, same input.

Withdraw mobile app request

mobile.withdraw_test_accesswrite

Take one of this account's tester requests back off the queue, so nobody adds that address to the store's tester list. The record is kept (marked withdrawn) rather than deleted, and the same address can be requested again later. It does not remove anyone the store has ALREADY added — that has to be undone in Play Console or App Store Connect.

Parameters

Field	Type	Required	Description
request_id	string (uuid)	required	Id of the request to withdraw, from mobile.status.

Example

curl -X POST https://app.chirply.io/api/v1/actions/mobile.withdraw_test_access \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "request_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Test with your API key

Over MCP the same operation is the tool mobile_withdraw_test_access at https://app.chirply.io/api/mcp, same bearer token, same input.