Developer tools

GitLab in your product and your AI agents, through one API

The GitLab toolkit covers projects and their members, issues with comments, and merge requests, including opening and merging them. Through Connect, a product or AI agent works on the customer's GitLab.com repositories without building the integration or renewing tokens.

15 days to try it. No credit card.

POST https://connect.reportei.com/api/tools/gitlab_create_issue/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "id": "<id>",
    "title": "<title>"
  }
}
Example: the "Create issue" tool on an account your customer connected.

How it works

From a connected customer to the first GitLab call.

  1. 1

    Your customer connects the account

    Your system opens a Connect session for the toolkit and your customer connects their GitLab account. You get the connection id.

  2. 2

    Your product calls the tool

    A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.

  3. 3

    Connect handles the rest

    It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.

Use cases

What your product does with GitLab.

  • Issues from your product

    Create a GitLab issue from a bug report or support ticket in your app, assign it with a member id and keep it in sync with later comments.

  • Coding agents opening merge requests

    Let an AI agent push a branch elsewhere, open a merge request from source_branch into target_branch and check detailed_merge_status before merging.

  • Project status for stakeholders

    Read open issues and merge requests per project and show progress to people who do not use GitLab.

Tools

13 GitLab tools

See all 13 tools

Connection

How your customer connects the account

Official GitLab documentation

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/gitlab, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

Questions about the GitLab toolkit

Do I need to build against the GitLab API?

No. Connect ships 13 GitLab tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.

How does my customer connect their GitLab account?

With the mode the toolkit accepts: API key, OAuth with your product's app. Connect stores the credential encrypted and never returns it to your system.

Does it work with AI agents?

Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.

Does my customer need a Reportei account?

No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.