Build with SimplyMe
A platform worth building on has to be worth building on for other people too. Here is what the SimplyMe API will cover, the rules that come with it, and how to get in early.
Where we are
SimplyMe is pre-launch, so there is no public API yet. We are designing it alongside the product rather than bolting it on afterwards, and we will open a private developer preview before general availability. If you want to be in that preview, see early access below.
What is planned
| Surface | What it will let you do |
|---|---|
| Content API | Read and publish posts, images, videos and articles on behalf of a consenting member. |
| Studio import/export | Push designs into a member’s Creative Studio, or export finished designs out. |
| Music metadata | Look up track metadata and licence terms. Audio files themselves stay inside the platform. |
| Professional profile | Read a member’s résumé and work showcase with explicit consent, for ATS and portfolio integrations. |
| Webhooks | Subscribe to new posts, comments, mentions and referral events. |
| SDKs | TypeScript first, then Python. Thin wrappers over a documented REST surface. |
| Embeds | oEmbed support so a SimplyMe post renders anywhere. |
Auth and permissions
- OAuth 2.1 with PKCE. No password-based API access, ever.
- Granular, human-readable scopes:
posts:read,posts:write,studio:write,resume:read. Members see exactly what an app is asking for. - Short-lived access tokens with refresh rotation.
- Members can review and revoke any connected app from their settings at any time, and revocation is immediate.
resume:readrequires a separate, explicit confirmation each time. Career data is not bundled into a general grant.
Platform rules
The API exists to let members do more with their own content. It does not exist to extract data about other people.
- No scraping or bulk collection. Do not build datasets of members, posts or résumés. This is the fastest way to lose access.
- No reselling candidate data. Résumé and profile data may only be used for the role the member consented to.
- No engagement automation. No auto-follow, auto-like, bulk DMs or metric manipulation.
- Store only what you need, delete it when a member disconnects your app, and honour deletion requests we forward to you.
- Respect our content rules. Everything in the Community Guidelines and Terms of Service applies to content your app publishes.
- Label AI output. Media your app generates or alters with AI must carry the label. See AI transparency.
- Do not imply endorsement. Brand asset rules are in our brand guidelines.
Rate limits and reliability
- Per-app and per-member limits, published in the reference docs and returned in headers.
429responses includeRetry-After. Back off exponentially rather than hammering.- Idempotency keys on all write endpoints so a retry cannot double-post.
- Breaking changes get a new version and at least 6 months of overlap.
- Deprecations are announced on this page and by email to registered developers.
- Incidents are posted to system status.
AI endpoints
Caption, rewrite and alt-text generation will be available to apps, with the same rules that apply in the product:
- A member must trigger the generation. No background or bulk generation.
- Output must be shown to the member for review before it is published.
- We do not train on content sent through these endpoints.
- Résumé generation is not exposed to third-party apps. The consequences of getting that wrong are too high to hand off.
Security research
We welcome good-faith security research and we will not pursue legal action against researchers who follow our rules. The full disclosure policy, covering scope, timelines and what is off-limits, is on the Report a problem page. Send findings to security@simplyme.app.
Get early access
Email hello@simplyme.app with “Developer preview” in the subject line. Tell us what you want to build, which surfaces you need, and roughly what scale you expect. We are prioritising integrations that give members more control over their own work: portfolio sync, design tooling, ATS connections.
Reference docs, a changelog and a status feed will all live under /developers once the preview opens.