source-commercetools: new capture connector - #5032
Merged
Merged
Conversation
Alex-Bair
force-pushed
the
bair/source-commercetools
branch
2 times, most recently
from
August 8, 2026 14:19
7f10776 to
57b7644
Compare
Alex-Bair
marked this pull request as ready for review
August 8, 2026 14:21
nicolaslazo
previously approved these changes
Aug 10, 2026
nicolaslazo
left a comment
Contributor
There was a problem hiding this comment.
Looks great! No comments
Alex-Bair
added a commit
to estuary/flow
that referenced
this pull request
Aug 10, 2026
Documentation updates for estuary/connectors#5032.
Alex-Bair
added a commit
to estuary/flow
that referenced
this pull request
Aug 10, 2026
Documentation updates for estuary/connectors#5032.
This commit introduces a new connector `source-commercetools` that captures orders, customers and payments from commercetools' HTTP API. Streams: orders, customers, payments backfill + incremental All three share one implementation. Every commercetools Query endpoint returns the same `PagedQueryResponse` envelope and gives its resources the same `id`/`lastModifiedAt` pair, so the streams differ only by path. commercetools caps `offset` at 10,000, which rules out offset paging on any real `Project`, so paging is keyset throughout. The incremental sweep sorts by `(lastModifiedAt, id)` and resumes on a compound predicate past the last document read. The backfill walks `id` ascending. This connector was built without commercetools credentials. Endpoint shapes come from commercetools' published API reference. There is deliberately no test_capture, since it would need a real account. Discovery's permission check is skipped for the `TEST_CONFIG_PROJECT_KEY` sentinel -- a value no Project can hold, as commercetools keys cannot contain a dot -- so spec and discover both run offline.
Alex-Bair
force-pushed
the
bair/source-commercetools
branch
from
August 10, 2026 16:27
57b7644 to
cc30016
Compare
Member
Author
|
Post-approval, I made a couple edits to the docs based on feedback I received in estuary/flow#3332. |
Alex-Bair
added a commit
to estuary/flow
that referenced
this pull request
Aug 10, 2026
Documentation updates for estuary/connectors#5032.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regression?
No.
Description:
This PR introduces a new, minimal connector
source-commercetoolsthat captures orders, customers and payments from commercetools' HTTP API.Notes for reviewers:
This capture connector was created with the
create-capture-connectorskill with development credentials for the commercetools API. Those dev credentials expire after the 60 day free trial expires though, so we can't use them long-term for discover and capture snapshot tests.Checklist:
CHANGELOG.mdand documentation have been updated (see CONTRIBUTING.md). TheDocs / CHANGELOG checkCI job reviews this automatically; apply thedocs-check-skiplabel to dismiss a false positive.