Runpod•5mo ago

Configuring endpoints via API if publishing via Github integration

It seems that there's no way to create / update endpoints via the API, unless you host the images on a docker registry.
Are there plans to extend API support to endpoints that are published from a github branch?

I want to have my full endpoint configuration and deployment via codel but this doesn't seem to be possible using the github integration, as opposed to deploying from a container registry.

From my findings, but I might be wrong:

GitHub templates are not regular templates:
   - They appear in template list but return 404 on direct access
   - They have auto-generated names like "[endpoint name]__template__00vc58"
   - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit}
What you CAN update via API:
   - All endpoint settings (workers, timeouts, scaling, etc.)
   - Switch between different template versions
   - Endpoint name and configuration
What you cannot update via API:
   - Template environment variables
   - Docker CMD/ENTRYPOINT overrides
   - Container disk size
   - Any template-level settings

GitHub templates are not regular templates:
   - They appear in template list but return 404 on direct access
   - They have auto-generated names like "[endpoint name]__template__00vc58"
   - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit}
What you CAN update via API:
   - All endpoint settings (workers, timeouts, scaling, etc.)
   - Switch between different template versions
   - Endpoint name and configuration
What you cannot update via API:
   - Template environment variables
   - Docker CMD/ENTRYPOINT overrides
   - Container disk size
   - Any template-level settings

GitHub templates are not regular templates:
   - They appear in template list but return 404 on direct access
   - They have auto-generated names like "[endpoint name]__template__00vc58"
   - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit}
What you CAN update via API:
   - All endpoint settings (workers, timeouts, scaling, etc.)
   - Switch between different template versions
   - Endpoint name and configuration
What you cannot update via API:
   - Template environment variables
   - Docker CMD/ENTRYPOINT overrides
   - Container disk size
   - Any template-level settings

GitHub templates are not regular templates:
   - They appear in template list but return 404 on direct access
   - They have auto-generated names like "[endpoint name]__template__00vc58"
   - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit}
What you CAN update via API:
   - All endpoint settings (workers, timeouts, scaling, etc.)
   - Switch between different template versions
   - Endpoint name and configuration
What you cannot update via API:
   - Template environment variables
   - Docker CMD/ENTRYPOINT overrides
   - Container disk size
   - Any template-level settings

Original thread: ⚡｜serverlessConfiguring endpoints via API if publishing via Github integration

nathaniel•7/30/25, 1:00 PM

ahh yeah this was a case of github integration endpoints being developed independently at the same time as the rest api and me not having time to readjust everything to use the new config options for those

Dj•7/30/25, 10:07 PM

I'll have this looked into, thanks for calling it out :fbslightsmile:

Configuring endpoints via API if publishing via Github integration

Similar Threads

Similar Threads

Similar Threads