Data types in Bubble are stored internally by their ID, but the Object API identifies them using the Display name — lowercased with spaces removed. This inconsistency means a plugin can't reliably look up a type by name from the API side. Types with special characters or names that collide after lowercasing and removing spaces may not be accessible at all.
What you might notice
Type names in plugin code don't match what you see in the editor
Types with special characters aren't visible through the Object API
Two types whose names become identical after lowercasing and removing spaces appear to overlap or mask each other
Workaround
Use your app's swagger.json file to programmatically list your API's data types. This lets you infer type names from the fields shown, even though type IDs aren't directly exposed. Fixing this inconsistency would require a breaking change to the plugin API, so it's planned as part of a future version update.