What you can build
- Music apps — browse and stream the full Anghami catalog: songs, albums, artists, playlists, lyrics, charts, and editorial sections.
- Video apps — browse and stream the OSN+ library: shows, seasons, episodes, and movies.
- Cross-content experiences — uniquely surface the soundtrack of a show or the shows that feature a song through
SoundtrackService. - Personal libraries — read a user’s liked songs, saved movies/shows, followed artists, and playback history.
- Server-to-server integrations — programmatic access via API key for catalog browsing without user context.
- AI agents — point any agent at this API and it can discover the OpenAPI spec, OAuth flow, and an
llms.txtbriefing automatically. See Agent Discovery.
What’s inside
| Area | Service |
|---|---|
| Music catalog | MusicCatalogService |
| Video catalog | VideoCatalogService |
| Search & browse | DiscoveryService |
| Cross-content | SoundtrackService |
| Playlists | PlaylistService |
| User library | LibraryService |
| Stream acquisition | StreamingService (billable) |
| User profile | UserService |
| OAuth | AuthService |
| API key management | DeveloperService |
/api/anghami-sdk.openapi.yaml. Drop it into Postman, Insomnia, or any OpenAPI codegen — one file, every operation.
Design tenets
- Proto-first.
.protofiles are the source of truth. Every client, doc, and HTTP handler is generated. - Cursor pagination everywhere. No offset/limit — see
PaginationRequest. - Typed IDs.
SongID,AlbumID,EpisodeID, etc. — never rawint64. - Stream acquisition is the billable event. No separate playback-reporting RPCs —
AcquireMusicStreamandAcquireVideoStreamare the only events that count. - Agent-native. OpenAPI bundle,
llms.txt, and a documented OAuth flow let any agent self-onboard.
Next steps
- Quickstart — get a token and make your first call in under five minutes.
- Architecture — how the SDK is organized and generated.
- Authentication — API key vs OAuth + PKCE.
- Agent Discovery — point an LLM at the SDK and let it self-configure.