OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Issue collections provide paginated JSON including timestamps, labels and project identifiers. Some premium fields have edition-specific behavior.
GitLab issue API ↗
List issues, filters, tier notes and pagination · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Issue collections provide paginated JSON including timestamps, labels and project identifiers. Some premium fields have edition-specific behavior.
GitLab issue API ↗
List issues, filters, tier notes and pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Issue queries accept state, labels, search and updated_after/before predicates. Project identifiers and issue-local IIDs must remain distinct.
GitLab issue API ↗
List issues, filters, tier notes and pagination · Checked 2026-10-16
Access cost barrier -
-
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Core issue endpoints are documented across Free, Premium and Ultimate, but complete commercial conditions of the assessed OAuth/export portfolio remain unresolved.
GitLab.com API limits ↗
General and endpoint-specific limits · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Registered OAuth applications act for the authorizing user within granted scopes. Project roles and organization policies constrain confidential issues, webhook management and export permissions.
GitLab OAuth authorization ↗
User authorization and registered OAuth applications · Checked 2026-10-16
Downstream permission -
-
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
GitLab OAuth authorization ↗
User authorization and registered OAuth applications · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
The Issues API documents create, edit and delete operations subject to project access and issue permissions.
GitLab issue mutation operations ↗
Create, edit and delete an issue · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Customers can build or choose applications using the documented API and the disclosed authorization route.
GitLab OAuth authorization ↗
User authorization and registered OAuth applications · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Updated-time issue polling and work-item notifications provide refresh mechanisms. Webhook management includes event inspection and resend; these do not establish a complete ordered deletion stream.
GitLab work-item webhook events ↗
Work item events and payload structure · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
GitLab.com publishes general and endpoint-specific rate limits, including separate issue-creation governors. Do not apply self-managed configurable limits to every GitLab.com account.
GitLab.com API limits ↗
General and endpoint-specific limits · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Issue updated_after identifies updates; complete issue deletion identity coverage across current work-item transitions remains unresolved.
GitLab work-item webhook events ↗
Work item events and payload structure · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Project webhook events can be inspected and resent within documented endpoint constraints; no full-history consumer checkpoint is established.
GitLab webhook management and resend ↗
List webhook events and resend an event · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Project file exports include selected project data and support a later GitLab import, with explicit omitted resources. API issues provide another portable record copy; this review does not claim a complete hosted project backup.
GitLab project file exports ↗
Exported items and items not exported · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
GitLab project file exports ↗
Exported items and items not exported · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Project file exports include selected project data and support a later GitLab import, with explicit omitted resources. API issues provide another portable record copy; this review does not claim a complete hosted project backup.
GitLab project file exports ↗
Exported items and items not exported · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
GitLab OAuth authorization ↗
User authorization and registered OAuth applications · Checked 2026-10-16
Rights to custom logic -
-
GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
GitLab OAuth authorization ↗
User authorization and registered OAuth applications · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Registered OAuth applications act for the authorizing user within granted scopes. Project roles and organization policies constrain confidential issues, webhook management and export permissions.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Issue collections provide paginated JSON including timestamps, labels and project identifiers. Some premium fields have edition-specific behavior. Issue queries accept state, labels, search and updated_after/before predicates. Project identifiers and issue-local IIDs must remain distinct.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Core issue endpoints are documented across Free, Premium and Ultimate, but complete commercial conditions of the assessed OAuth/export portfolio remain unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The Issues API documents create, edit and delete operations subject to project access and issue permissions.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Updated-time issue polling and work-item notifications provide refresh mechanisms. Webhook management includes event inspection and resend; these do not establish a complete ordered deletion stream. GitLab.com publishes general and endpoint-specific rate limits, including separate issue-creation governors. Do not apply self-managed configurable limits to every GitLab.com account.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Issue updated_after identifies updates; complete issue deletion identity coverage across current work-item transitions remains unresolved. | GitLab work-item webhook events ↗Work item events and payload structureChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Project webhook events can be inspected and resent within documented endpoint constraints; no full-history consumer checkpoint is established. | GitLab webhook management and resend ↗List webhook events and resend an eventChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Project file exports include selected project data and support a later GitLab import, with explicit omitted resources. API issues provide another portable record copy; this review does not claim a complete hosted project backup.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Issue collections provide paginated JSON including timestamps, labels and project identifiers. Some premium fields have edition-specific behavior. | GitLab issue API ↗List issues, filters, tier notes and paginationChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Issue collections provide paginated JSON including timestamps, labels and project identifiers. Some premium fields have edition-specific behavior. | GitLab issue API ↗List issues, filters, tier notes and paginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Issue queries accept state, labels, search and updated_after/before predicates. Project identifiers and issue-local IIDs must remain distinct. | GitLab issue API ↗List issues, filters, tier notes and paginationChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Registered OAuth applications act for the authorizing user within granted scopes. Project roles and organization policies constrain confidential issues, webhook management and export permissions. | GitLab OAuth authorization ↗User authorization and registered OAuth applicationsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Core issue endpoints are documented across Free, Premium and Ultimate, but complete commercial conditions of the assessed OAuth/export portfolio remain unresolved. | GitLab.com API limits ↗General and endpoint-specific limitsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | GitLab OAuth authorization ↗User authorization and registered OAuth applicationsChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. The Issues API documents create, edit and delete operations subject to project access and issue permissions. | GitLab issue mutation operations ↗Create, edit and delete an issueChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Customers can build or choose applications using the documented API and the disclosed authorization route. | GitLab OAuth authorization ↗User authorization and registered OAuth applicationsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Updated-time issue polling and work-item notifications provide refresh mechanisms. Webhook management includes event inspection and resend; these do not establish a complete ordered deletion stream. | GitLab work-item webhook events ↗Work item events and payload structureChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. GitLab.com publishes general and endpoint-specific rate limits, including separate issue-creation governors. Do not apply self-managed configurable limits to every GitLab.com account. | GitLab.com API limits ↗General and endpoint-specific limitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Project file exports include selected project data and support a later GitLab import, with explicit omitted resources. API issues provide another portable record copy; this review does not claim a complete hosted project backup. | GitLab project file exports ↗Exported items and items not exportedChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | GitLab project file exports ↗Exported items and items not exportedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | GitLab OAuth authorization ↗User authorization and registered OAuth applicationsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | GitLab OAuth authorization ↗User authorization and registered OAuth applicationsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate. Project file exports include selected project data and support a later GitLab import, with explicit omitted resources. API issues provide another portable record copy; this review does not claim a complete hosted project backup. | GitLab project file exports ↗Exported items and items not exportedChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.