Developers

On this page
Start

Blazot API · v2

Build on Blazot

Read Blazot's public content from your own server: users, Sites, transmissions, hashtags, hubs, events, catalogs and classified ads.

Requests go to https://api.blazot.com over HTTPS, with an access token you get from your own API key. Version 2 reads what's public on Blazot, as your account sees it.

What you can do

  • Read accounts: users' and Sites' public profiles, and a user's followers and following.
  • Read transmissions: an account's timeline, a hashtag's feed, a hub's feed, or a single transmission, with their media, polls and link previews.
  • Keep up with new transmissions: the user, Site and hashtag feeds can be polled for what's new since your last read.
  • Browse the rest: hub categories and members, Site events and catalogs, classified ads and their categories, user and hashtag search, and the emoticon set.

Every endpoint, its parameters and a sample response are in the API reference.

How it works

  • Your own keys. You create an API key and its secret on Blazot, for your account or for a Site you manage. The API reads as that account: it sees what that account would see on Blazot.
  • Read-only. Version 2 reads; it doesn't send transmissions or change anything on Blazot.
  • From your server. The API allows no cross-origin requests, so a web page in a browser can't call it, and your secret must never be in a web page or an app. Call it from your own server, and send the results to your pages from there.

Where to start

  1. Quickstart: check the API is up, get a token and make your first read, in curl, C#, JavaScript or Python.
  2. Concepts: users and Sites, transmissions, relays, hubs and media, and how the account behind your key changes what you see.
  3. Authentication: tokens, how long they last, and what makes one stop working.
  4. Errors: what each error means and what to do about it.

Keep your secret safe

Warning

Anyone who has your key and secret can read as you. Keep them in a secret store on your server, never in a web page, an app or your source code. If they leak, regenerate them on your Configuration page (or the Site's, for a Site's key): your old key and every token it issued stop working at once.