It should work. Look here for more details.
Saying that, I would recommend creating separate APIs for the different stages. Just like you created different backends, create different APIs. This way you reduce the risk that when you change something in dev it will accidentally impact production. I would even recommend creating the different environments in different accounts.
Http API Gateway with lambda integration for multiple routesAccepted Answerasked 2 years ago
Build a REST API with API Gateway private integration: TutorialAccepted Answerasked 7 months ago
Can I use API Gateway cache invalidation with a custom authorizer ?asked 8 months ago
Return a custom header from lambda authorizer in API-gateway (HTTP api)asked 4 months ago
Http API Gateway using stage variables on a private integrationasked 9 months ago
API Gateway Private Integration with multiple NLB listenersAccepted Answerasked 3 years ago
Trying to use a single Amazon API Gateway endpoint to accept both HTTP and websocket requestsAccepted Answerasked 2 years ago
API Gateway: AWS Service integration using IAM authorizationasked 2 months ago
API Gateway - Gateway response - HTTP APIAccepted Answerasked 2 years ago
HTTP API Gateway: Specifying Different Lambda Version per StageAccepted Answerasked 8 months ago