Runscope API

Name: Runscope API API
Brand: Runscope API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliveryoauth229 EndpointsREST

For Agents

Programmatically account resource, create a new bucket. Covers 29 operations with oauth2 authentication.

Use for: I need to account resource, I want to a new bucket, Search for returns a list of buckets., Find all returns a single bucket resource.

Quickstart

Get started with Runscope API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"account resource"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Runscope API API.

Account Resource

Create a new bucket

Returns a list of buckets.

Delete a single bucket resource.

Monitor Runscope API operational status and events

GET STARTED

Start building with Runscope API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Runscope API API for, with concrete tasks.

★ Communications Operations

Use the Runscope API to perform communications operations programmatically. The API provides 29 endpoints covering core functionality including account resource, create a new bucket, returns a list of buckets..

Call GET /account to account resource

Automated Account Management

Automate account operations by combining multiple Runscope API endpoints. Agents can create a new bucket and then returns a list of buckets. in a single workflow.

Call POST /buckets to create a new bucket, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Runscope API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Search Jentic for 'account resource', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

29 endpoints — manage runscope programmatically.

METHOD

PATH

DESCRIPTION

GET

/account

Account Resource

POST

/buckets

Create a new bucket

GET

/buckets

Returns a list of buckets.

GET

/buckets/{bucketKey}

Returns a single bucket resource.

DELETE

/buckets/{bucketKey}

Delete a single bucket resource.

POST

/buckets/{bucketKey}/environments

Create new shared environment.

GET

/buckets/{bucketKey}/environments

Returns list of shared environments for a specified bucket.

PUT

/buckets/{bucketKey}/environments/{environmentId}

Update the details of a shared environment.

GET

/account

Account Resource

POST

/buckets

Create a new bucket

GET

/buckets

Returns a list of buckets.

GET

/buckets/{bucketKey}

Returns a single bucket resource.

DELETE

/buckets/{bucketKey}

Delete a single bucket resource.

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Runscope API oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'account resource') and Jentic returns the matching Runscope API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Runscope API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Runscope API API through Jentic.

What authentication does the Runscope API use?

The Runscope API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I account resource with the Runscope API?

Yes. Use the GET /account endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Runscope API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I account resource through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'account resource'. Jentic returns the matching Runscope API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Runscope API have?

The Runscope API exposes 29 endpoints covering account, buckets, teams operations.