There were several errors in the Platform API reference docs that I just published, now that I'm able to actually fully test the production endpoints. The biggest ones in this first follow-on PR are:

• The URL to call the API is slightly off: https:// instead of http://. Switching from HTTP to HTTPS was a relatively last-minute back-end update. In the meantime, our more tech-savvy customers should be able to figure this out.
• Instructions for changing (not creating) source and destination connectors are wrong, as name and type should not be specified. In the meantime, customers might be able to figure this out by cross-referencing the Swagger UI, but this is certainly not intuitive.
• Some of the query parameters for listing workflows are wrong. In the meantime, customers might be able to figure this out by cross-referencing the Swagger UI, but this is certainly not intuitive.
• Instructions for creating workflows are wrong, specifically around setting repeating workflow run schedules. In the meantime, customers might be able to figure this out by cross-referencing the Swagger UI, but this is certainly not intuitive.

(The second follow-on PR, of a slightly lower priority, is to backfill instructions for creating some of the source and destination connectors that are missing, as these connectors were brought online just a few days ago. The field names for these connectors do not match 1:1 with the related labels in the UI, and they are not exposed in the Swagger UI either, so without these docs it will be almost impossible to figure them out. These are; sources: Couchbase, Dropbox, Elasticsearch, Google Drive, and Salesforce; and destinations: Destinations: Couchbase, PostgreSQL, and Qdrant.)