Substratal Apps Substratal Apps Hub specs
GitHub

Help Screens Applications

Push credentials APL-07

Configure APNs, FCM and Web Push for an Application so it can send push notifications.

Who can use itOwner or applications.manage with a User token (write); app key / owner (read)
Where it is/dev/apps/:appId/push · link: https://hub.substratalapps.com/dev/apps/:appId/push or substratal://dev/apps/:appId/push
Available onWeb (PWA), iOS / iPadOS, Android, Windows, Linux (GNOME), macOS
PhasePhase 2

What you can do here

  • Add — 201; 409 push_credential_exists → Edit; 422 invalid_push_credential → field error; 400 user_token_required never happens in the Hub (User token)
  • Fetch one — on Edit
  • Save — 409 invalid_status_transition
  • Remove — 204

On your platform

AppStatusHow it's built
Web (PWA)—tabpanel (route segment)
iOS / iPadOS—Segment content
AndroidPlannedTab content
Windows—SelectorBar item content
Linux (GNOME)—AdwViewStack page
macOS—Tab content inside detail

Status is reported by each app's repository; — means that app doesn't report it yet.

For developers: API calls

MethodPathWhat it does
GET/applications/{id}/push-credentialsList the push providers an Application has configured (the owner, the app's own key, or applications.manage)
POST/applications/{id}/push-credentialsConfigure one push provider (the owner or applications.manage, User token only)
GET/applications/{id}/push-credentials/{provider}Fetch one provider's configuration
PATCH/applications/{id}/push-credentials/{provider}Replace key material, change non-secret fields, or re-enable a failed credential (User token only)
DELETE/applications/{id}/push-credentials/{provider}Remove a push provider (User token only)

Every call sends Substratal-Version: 1. Paths are at the host root, with no /v1.

Full screen specification

Last updated 2026-10-24 · Built 2026-10-25 from a9ef3be · API 1.0.0-draft.13 · Substratal-Version: 1