> ## Documentation Index
> Fetch the complete documentation index at: https://docs.manypi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Invoke an endpoint

> Call one of your published endpoints.

How a call resolves: a fresh cached result is returned immediately (no crawl credits spent); otherwise the scrape runs inline, up to a ~110 second budget; if it exceeds that — or the endpoint is `async` — you get `202` with a run id to poll at `GET /v1/e/{slug}/results/{runId}`.

Requires the `endpoints:invoke` permission.



## OpenAPI

````yaml GET /v1/e/{slug}
openapi: 3.1.0
info:
  title: ManyPI API
  description: >-
    The REST API behind ManyPI — AI lead generation, email validation,
    cold-email outreach, agent runs and web scraping. Every endpoint is
    authenticated with a ManyPI API key (`mpi_...`) or an OAuth 2.1 access
    token, and honours the permissions granted to that credential.
  version: 2.0.0
  contact:
    name: ManyPI Support
    email: support@manypi.com
    url: https://manypi.com
servers:
  - url: https://app.manypi.com
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Leads
    description: Find, store, enrich and manage leads.
  - name: Email validation
    description: Verify that lead addresses can receive mail.
  - name: Outreach
    description: Inboxes, sequences, campaigns, sending and replies.
  - name: Agent
    description: Agent runs, replies and skills.
  - name: Scraping
    description: Scrapers, runs and extracted data.
  - name: Endpoints
    description: Publish scrapers as typed REST endpoints.
  - name: Account
    description: Key validation and account information.
paths:
  /v1/e/{slug}:
    get:
      tags:
        - Endpoints
      summary: Invoke an endpoint
      description: >-
        Call one of your published endpoints.


        How a call resolves: a fresh cached result is returned immediately (no
        crawl credits spent); otherwise the scrape runs inline, up to a ~110
        second budget; if it exceeds that — or the endpoint is `async` — you get
        `202` with a run id to poll at `GET /v1/e/{slug}/results/{runId}`.


        Requires the `endpoints:invoke` permission.
      operationId: invokeEndpoint
      parameters:
        - name: slug
          in: path
          required: true
          schema:
            type: string
        - name: url
          in: query
          description: Endpoint-defined parameters, validated against its `param_schema`.
          schema:
            type: string
      responses:
        '200':
          description: The extracted data, matching the endpoint's output schema.
          content:
            application/json:
              schema:
                type: object
        '202':
          description: Still running. Poll `GET /v1/e/{slug}/results/{runId}`.
          content:
            application/json:
              schema:
                type: object
                properties:
                  runId:
                    type: string
                    format: uuid
                  status:
                    type: string
        '400':
          description: Parameters failed validation against the endpoint's schema.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          description: The key lacks the `endpoints:invoke` permission.
        '404':
          description: No endpoint with that slug for this account.
components:
  responses:
    Unauthorized:
      description: >-
        Missing, invalid or expired credential — or a key that lacks the
        permission this route requires.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable message.
        code:
          type: string
          description: >-
            A machine-readable code on gated failures: `lead_limit`,
            `outreach_locked`, `validation_credits_exhausted`.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A ManyPI API key (`mpi_...`) from Settings → API keys, or an OAuth 2.1
        access token obtained through the MCP consent flow.

````