feat(source-bol): new connector

[newnorthdigital]

What

New community source connector for bol.com (the largest online retail platform in the Netherlands/Belgium), built on the Retailer API v10. Manifest-only / low-code.

Streams:

• orders — incremental on Bol's latest-change-date filter. NB: live-verified that this filter is an exact-day filter (not "since"), so the cursor slices per day (step P1D), floored at 89 days back (API limit).
• order_details — the only stream with money fields (unitPrice, commission); follows an FBB-only parent stream to respect the much stricter per-order rate limit (rationale in the docs).
• returns — unions the handled=false/true partitions.
• shipments, inventory — snapshots (the API exposes no change filter).

Auth: OAuth2 client-credentials against login.bol.com (299s tokens, self-refreshing). 429s honor Bol's Retry-After.

Why

No Bol connector exists in the registry today, while bol.com is the dominant marketplace for NL/BE ecommerce sellers. Running in production at New North Digital since June 2026 across multiple seller accounts; we maintain it.

How tested

• Live-validated against three production seller accounts (check/discover/read; incremental state verified across syncs).
• The exact-day cursor semantics, body-credential OAuth acceptance and Retry-After behavior were all verified against the live API (documented in the docs page's Limitations section).
• Sandbox credentials for CAT can be provided to reviewers on request.

Docs

User-facing docs added at docs/integrations/sources/bol.md, including the 3-month order-history caveat and the exact-day filter behavior.

🤖 Generated with Claude Code

[octavia-bot]

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

[github-actions]

👋 Welcome to Airbyte!

Thank you for your contribution from newnorthdigital/airbyte! We're excited to have you in the Airbyte community.

If you have any questions, feel free to ask in the PR comments or join our Slack community.

💡 Show Tips and Tricks

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
• /run-connector-tests - Runs connector tests.
• /run-cat-tests - Runs CAT tests.
• /run-regression-tests - Runs regression tests for the modified connector(s).
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
• /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
• /ai-review - AI-powered PR review for connector safety and quality gates.
• /ai-docs-review - AI-powered documentation review for PRs with connector changes.
• /ai-create-docs-pr - Creates a documentation PR for connector changes.
• /force-merge reason="<A_GOOD_REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.

Tips for Working with CI

1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
   • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

📚 Show Repo Guidance

Helpful Resources

• Maintainers: AI-SDLC Docs (internal link)
• PR Guidelines: Check our guidelines for contributions.
• Breaking Changes Guide: Guide to breaking changes, migration guides, and upgrade deadlines.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

📝 Edit this welcome message.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}