Read-only EAS billing API for third-party OAuth apps
Alderik
Use case
I build Vibe Costs, a dashboard that lets developers aggregate live software and infrastructure costs. EAS Billing already shows an estimated current-period amount across Build, Update, Hosting, and Workflows, but there is no public endpoint or billing-read OAuth scope for reading that summary.
Expo billing support confirmed that the EAS REST API only covers triggering workflows and reading run details. Personal access tokens and robot users are the documented programmatic options, but robot users still cannot read cost data.
Requested solution
Please add customer-authorized third-party OAuth with a narrow billing-read scope and an endpoint returning:
- current billing-period total and currency
- plan allowance and signed credits or adjustments
- documented freshness
- EAS product and project attribution
- stable account, project, and resource IDs
The important constraint is least privilege. Customers should not need to provide a personal access token or robot token to an external cost dashboard.
Technical proposal and machine-readable schema:
If this becomes available, I will build and maintain the connector and test it against my own Expo account.