Skip to main content

Connect DevCycle

1 auth method · updated 2026-10-01

DevCycle is a feature management platform for creating, targeting, releasing, and monitoring feature flags across applications.

devcycle.com ↗

Server-to-server OAuth

Server-to-server OAuth

Guide only — not directly connectable

Server-to-server OAuth uses client credentials from DevCycle’s developer console. Verslay’s connect form doesn’t support it for this toolkit yet.

  1. 1
    Create a server-to-server app
    In DevCycle’s developer console, create an app that uses the server-to-server (client credentials) flow.
  2. 2
    Copy the credentials
    You’ll need the client ID and the client secret from the app’s settings page.
  3. 3
    Not yet connectable in Verslay
    Verslay’s connection form doesn’t support server-to-server OAuth for DevCycle yet. The method is documented here so you know exactly what it requires.

What you’ll paste into Verslay

Management API Client ID

The Client ID from your DevCycle dashboard under Settings > API Authentication. DevCycle presents this Client ID and its paired Client Secret as a Management API Key.

required
Management API Client Secret

The Client Secret paired with your Management API Client ID in the DevCycle dashboard under Settings > API Authentication. Keep this value secret.

required · secret
Get your credential ↗DevCycle website ↗

DevCycle connection FAQ

How do I connect DevCycle to Verslay?

DevCycle cannot be connected directly from Verslay yet. This page documents what each method requires so you know what to expect.

What do I need before I connect DevCycle?

An account with DevCycle.

Related connection guides

See also Verslay use cases and agents.

Connect DevCycle once — every agent can use it

Verslay agents share your connections. Connect DevCycle in the Hub and every use-case that needs it lights up — no per-agent setup.

Open the Hub →
← All connection guides