Skip to main content

Apps

An App connects an outside tool or a piece of software your organization uses to Typograph, so it can work with your projects and templates on your behalf. You'll need one before connecting anything external — a custom integration, an internal tool, or a webhook.

Only an owner or admin of the organization can create or delete apps, or change an app's logo or IP addresses. Members see the list and each app's details; the New App, Logo, IP addresses and Delete actions are not shown to them. See Permissions.

Creating an App​

  1. Go to Organizations → {Your Org} → Apps.
  2. Click New App.
  3. Give the app a name — this is how it'll show up in your app list.
  4. Add its redirect URIs — the web addresses Typograph is allowed to send you back to once you've approved the connection. Add one for each place the app runs (for example, your test environment and your live one).
  5. Select the scopes the app needs — these are the specific permissions it's asking for. Only grant what the integration actually needs.
  6. Save. The app now has a client ID and secret it can use to connect.

Viewing or Removing an App​

  1. Go to Organizations → {Your Org} → Apps.
  2. Select the app to see its details — name, redirect URIs, and granted permissions.
  3. Click Delete to remove it.

Deleting an app immediately cuts off its access. Anything that was using it — including any webhook attached to it — stops working.

An app that people sign in to (one with a redirect URI) shows its logo on the consent screen, where they decide whether to give it access to their Typograph account. Without one, they see a grey placeholder.

  1. Go to Organizations → {Your Org} → Apps.
  2. Open the ⋯ menu of the app and choose Logo.
  3. Choose a square PNG, JPG or WebP image of 128 to 1024 pixels per side, at most 512 KB. 256 × 256 pixels looks sharp everywhere. The portal shows the image before you save and says which requirement it misses.
  4. Click Save logo. Remove logo brings back the placeholder.

Typograph does not crop or resize the image, so make it square yourself, with some space around the mark. More detail for developers: API → Authentication.

Limiting an App to IP Addresses​

An app that runs on your own server can be limited to the addresses that server uses. Its client ID, secret and tokens then work from those addresses only, so a secret that leaks is of no use anywhere else.

  1. Go to Organizations → {Your Org} → Apps.
  2. Open the ⋯ menu of the app and choose IP addresses.
  3. Write the addresses, one per line: a single address such as 203.0.113.7, or a range such as 203.0.113.0/24. IPv4 and IPv6 both work, up to 50 lines.
  4. Click Save addresses.

Within a minute the app stops working from any other address, also with tokens it already has. Ask whoever runs the app which addresses its server sends from before you save. Allow every address lifts the limit again. The app's details show the list, or Any address.

The portal shows your own address as you open the window. Add it only when the app runs on the network you are on, for instance while you test it.

An app that runs in a browser or on a phone (one without a secret) has no IP addresses action: its users' addresses cannot be listed. More detail for developers: API → Authentication.