Skip to main content

tap-bitly

Singer tap for Bitly. Built with the Meltano Singer SDK.

Capabilities

  • catalog
  • state
  • discover
  • about
  • stream-maps
  • schema-flattening

Settings

Setting Required Default Description
token True None API Token for Bitly
include_paid_streams False False Whether to sync paid streams
start_date False None Earliest datetime to get data from
stream_maps False None Config object for stream maps capability. For more information check out Stream Maps.
stream_map_config False None User-defined config values to be used within map expressions.
flattening_enabled False None 'True' to enable schema flattening and automatically expand nested properties.
flattening_max_depth False None The max depth to flatten schemas.

Supported Streams

Stream Name Endpoint Notes
groups /v4/groups
bitlinks /v4/groups/{group_guid}/bitlinks
bsds /v4/bsds
campaigns /v4/campaigns
channels /v4/channels
organizations /v4/organizations
webhooks /v4/organizations/{organization_guid}/webhooks Requires paid account
daily_bitlink_clicks /v4/bitlinks/{bitlink}/clicks
monthly_bitlink_clicks /v4/bitlinks/{bitlink}/clicks

A full list of supported settings and capabilities is available by running: tap-bitly --about

Source Authentication and Authorization

Generate an access token from the Bitly API Console.

Usage

You can easily run tap-bitly by itself or in a pipeline using Meltano.

Executing the Tap Directly

tap-bitly --version
tap-bitly --help
tap-bitly --config CONFIG --discover > ./catalog.json

Developer Resources

Initialize your Development Environment

uv tool install --with tox-uv tox

Create and Run Tests

Run all tests:

tox run-parallel

Testing with Meltano

Note: This tap will work in any Singer environment and does not require Meltano. Examples here are for convenience and to streamline end-to-end orchestration scenarios.

Your project comes with a custom meltano.yml project file already created. Go ahead and install Meltano if you haven't already.

  1. Install all plugins

    meltano install
    
  2. Check that the extractor is working properly

    meltano invoke tap-bitly --version
    
  3. Execute an EL pipeline

    meltano run tap-bitly target-jsonl
    

SDK Dev Guide

See the dev guide for more instructions on how to use the SDK to develop your own taps and targets.

Metadata

Release files for tap-bitly 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tap-bitly 0.5.0
File Size Uploaded
tap_bitly-0.5.0.tar.gz 80.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for tap-bitly 0.5.0
File Interpreter ABI Platform
tap_bitly-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 114.7 kB

Release files / tap_bitly-0.5.0.tar.gz

Download URL tap_bitly-0.5.0.tar.gz
Size 80.9 kB
Tags Source
SHA-256 checksum
How to use checksums
124096610341605ea432d7c525f22392286eba42b8eabab67f08e02cf3d4cfe3
BLAKE2b-256 checksum
How to use checksums
6954e7e35beb7f731d4defa3902300208629a15bb0d8d173323b30f3cc530001
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 5, 2025.

Transparency log

Release files / tap_bitly-0.5.0-py3-none-any.whl

Download URL tap_bitly-0.5.0-py3-none-any.whl
Size 33.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b8349ab57aa531b8bf2eaf74402d08883678e1eae47131428cb046e8eddeb051
BLAKE2b-256 checksum
How to use checksums
849d1fe1e55c3cb9d235cf040fc3d5b66c0e4d3e7ad6e4776526370deac012b0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 5, 2025.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page