Services are applications that belong to an organization and use AuthOS for authentication. Use this overview to choose the smallest reference or task guide for the work you are doing.
Endpoint and task index
| Goal | Page |
|---|---|
| Create, list, inspect, update, or delete a service | Service endpoint reference |
| Create, list, update, or delete plans; start checkout | Plan and checkout reference |
| Configure Stripe-backed plans and complete a billing flow | Billing integration recipes |
| Review access, validation, OAuth, plan, and audit controls | Security and operations |
| Diagnose authorization, limits, deletion, or checkout failures | Troubleshooting |
What a service contains
- Client ID: Unique identifier for OAuth2 flows
- Service type: Web, mobile, desktop, or API categorization
- OAuth scopes: Custom GitHub, Google, and Microsoft provider scopes
- Redirect URIs: Allowed OAuth2 callback URLs
- Device activation URI: Optional device-flow destination
- Plans: Subscription tiers with pricing and features
- Usage tracking: Plan and subscription counts
Organizations have service limits based on their tier. Creating a service also provisions a default Free plan. Plan prices can be associated with Stripe Price IDs when billing is enabled.
Choose the right credential
Organization members use a bearer JWT for the management endpoints in this section. Service-to-service consumers should instead use the API Keys guide and the Service API reference.