If we're talking about an API key, then the issue isn't collision and there's no relationship with hashing or uuids except the recommended final length.
A key should be a random 128-bit string (or 192, or 256 if you need additional security).
If you need to generate a key from a passphrase, use a key expansion function, not an hash just because the length is the same.
I don't know if there's any proof of randomness for uuid, the risk (in absence of a proof) is that to provide uniqueness the bit distribution is uneven, which could leak some information to an attacker, thus reducing the real bit strength of the key.