feat: source-ramp contribution from MercureTony

[Anthony Uyende (MercureTony)]

What

This PR adds a new connector for source Ramp (source-ramp).

Contributor-provided connector description:

Syncs cards, transactions, and reimbursements from Ramp's developer API.

The contributor provided the following description of the change:

New source connector for Ramp (https://ramp.com). Three streams: cards (full refresh), transactions and reimbursements (incremental on updated_at, using the API's server-side updated_after filter). OAuth2 client-credentials auth against Ramp's developer API. Supersedes #81404 with that review's feedback applied: allowedHosts set to api.ramp.com and user-facing config descriptions.

Details

Expand for list of spec properties and streams

Configuration

Input	Type	Description	Default Value
client_id	string	Ramp Client ID. Your Ramp API client ID, created in Ramp's developer settings.
client_secret	string	Ramp Client Secret. Your Ramp API client secret.
start_date	string	Start Date. Earliest updated_at to pull on the initial sync of the transactions and reimbursements streams. Format ISO 8601 with Z suffix (e.g. 2024-01-01T00:00:00Z). Ignored on subsequent incremental syncs.

Streams

Stream Name	Primary Key	Pagination	Supports Full Sync	Supports Incremental
cards	id	DefaultPaginator	✅	❌
transactions	id	DefaultPaginator	✅	✅
reimbursements	id	DefaultPaginator	✅	✅

Reviewer checklist

• Consider how the connector handles pagination (docs).
• Help the contributor upload an icon that follows our icon design guidelines
• Click into the CI workflows that wait for a maintainer to run them, which should trigger CI runs

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ MercureTony
❌ claude
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[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 MercureTony/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.