Is the JFrog Artifactory REST API compatible with Bintray services?

Other Questions API
1

I’m trying to set up an automated build pipeline using Spinnaker that needs to fetch artifacts from my repository. My setup involves publishing Java packages to Bintray, and I want Spinnaker to automatically detect new artifacts and start deployments.

Spinnaker has built-in support for JFrog Artifactory repositories, so I thought I could point it directly at my Bintray repository. Here’s how I configured it:

hal config repository artifactory enable
hal config repository artifactory search add my-bintray \
           --base-url https://dl.bintray.com/myuser \
           --repo my-java-libs \
           --groupId com.mycompany \
           --username myuser \
           --password mytoken

But I keep getting HTTP 405 errors in the logs:

2019-08-15 14:20:00.262  WARN 1 --- [RxIoScheduler-3] c.n.s.i.a.ArtifactoryBuildMonitor        : Unable to query Artifactory for artifacts (HTTP 405):

I’m starting to think that Bintray doesn’t actually support the same REST API endpoints that Artifactory uses. Can anyone confirm if Bintray is compatible with Artifactory’s API, or do I need a different approach for this integration?

2

I encountered this same frustration when working with legacy Bintray repositories before the sunset. The APIs are fundamentally incompatible because Artifactory uses GAVC-based search endpoints while Bintray has its own repository structure and API conventions. What worked for me was bypassing Spinnaker’s Artifactory integration entirely and using the webhook approach instead. You can configure Bintray to send notifications to a webhook endpoint when new versions are published, then have Spinnaker listen for those events. The artifact URLs from Bintray webhooks can be used directly in your pipeline stages without needing the search functionality that’s causing your 405 errors. This approach actually ended up being more reliable than trying to poll for changes anyway.

3

yeah bintray and artifactory apis are totally different beasts even tho they’re both jfrog products. you’ll need to use bintray’s own api endpoints instead of trying to force the artifactory integration - that’s why you’re getting those 405s

4

You’re correct in your assumption - Bintray does not support Artifactory’s REST API endpoints. While both are JFrog products, they have completely different API structures and cannot be used interchangeably in tools that expect Artifactory-specific endpoints. I ran into this exact issue when migrating from Bintray to Artifactory last year. The HTTP 405 error you’re seeing occurs because Spinnaker is making API calls to endpoints that simply don’t exist in Bintray’s API. For your use case, you’ll need to configure Spinnaker to use Bintray’s native API instead of the Artifactory integration. This typically means setting up a custom webhook trigger from Bintray or using Spinnaker’s generic HTTP artifact support with Bintray’s download URLs. The configuration will be more manual but it’s the only way to properly integrate with Bintray repositories.